Data processing systems for orphaned data identification and deletion and related methods

ABSTRACT

In particular embodiments, an Orphaned Data Action System is configured to analyze one or more data systems (e.g., data assets), identify one or more pieces of personal data that are one or more pieces of personal data that are not associated with one or more privacy campaigns of the particular organization, and notify one or more individuals of the particular organization of the one or more pieces of personal data that are one or more pieces of personal data that are not associated with one or more privacy campaigns of the particular organization.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/216,436, filed Mar. 29, 2021, which is a continuation of U.S. patent application Ser. No. 17/068,557, filed Oct. 12, 2020, now U.S. Pat. No. 10,963,591, issued Mar. 30, 2021, which is a continuation of U.S. patent application Ser. No. 16/813,321, filed Mar. 9, 2020, now U.S. Pat. No. 10,803,202, issued Oct. 13, 2020, which is a continuation of U.S. patent application Ser. No. 16/563,735, filed Sep. 6, 2019, now U.S. Pat. No. 10,586,075, issued Mar. 10, 2020, which claims priority from U.S. Provisional Patent Application Ser. No. 62/728,435, filed Sep. 7, 2018. The disclosures of all of the above patent applications are hereby incorporated herein by reference in their entirety.

BACKGROUND

Over the past years, privacy and security policies, and related operations have become increasingly important. Breaches in security, leading to the unauthorized access of personal data (which may include sensitive personal data) have become more frequent among companies and other organizations of all sizes. Such personal data may include, but is not limited to, personally identifiable information (PII), which may be information that directly (or indirectly) identifies an individual or entity. Examples of PII include names, addresses, dates of birth, social security numbers, and biometric identifiers such as a person's fingerprints or picture. Other personal data may include, for example, customers' Internet browsing habits, purchase history, and even their preferences (e.g., likes and dislikes, as provided or obtained through social media).

Many organizations that obtain, use, and transfer personal data, including sensitive personal data, have begun to address these privacy and security issues. To manage personal data, many companies have attempted to implement operational policies and processes that comply with legal and organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example, a right to obtain confirmation of whether a particular organization is processing their personal data, a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected), and other such rights. Some regulations require organizations to comply with requests for such information (e.g., Data Subject Access Requests) within relatively short periods of time (e.g., 30 days).

Existing systems for complying with such requests can be inadequate for producing and providing the required information within the required timelines. This is especially the case for large corporations, which may store data on several different platforms in differing locations. Accordingly, there is a need for improved systems and methods for complying with data subject access requests.

SUMMARY

A method, according to various aspects, comprising: (1) accessing, by computing hardware, a data model that maps an association between personal data stored on a data asset and respective processing activities undertaken by an entity; (2) analyzing, by the computing hardware, the data model to identify a first portion of the personal data that is associated with a terminated processing activity of the processing activities; and (3) facilitating removal, by the computing hardware, of the first portion of the personal data from the data asset. In particular aspects, the method may further comprise: (1) analyzing, by the computing hardware, the data model to identify a second portion of the personal data that is not associated with any of the processing activities; and (2) facilitating removal, by the computing hardware, of the second portion of the personal data from the data asset. In some aspects, the method further comprises: (1) scanning, by the computing hardware, the data asset to identify the personal data stored on the data asset and the processing activities undertaken by the entity that utilize the data asset to generate a catalog of the personal data; and (2) scanning, by the computing hardware, the data asset based on the generated catalog to generate the data model.

In any aspect described herein, facilitating removal of the first portion of the personal data from the data asset comprises at least one of: (1) generating a user interface that includes an indication of the first portion of the personal data, or (2) generating and transmitting an instruction to a third party system regarding removal of the first portion of the personal data from the data asset. In still other aspects, the method further comprises: (1) accessing, by the computing hardware, data retention parameters for the data asset, wherein the data retention parameters comprise one or more of: (a) a first parameter defining a time period within which the personal data must be removed; and (b) a second parameter identifying a triggering event for removal of the first portion of the personal data. In some aspects, the method may further comprise facilitating the removal, by the computing hardware, of the first portion of the personal data from the data asset according to the data retention parameters by facilitating at least one of: (a) the removal of the personal data from the data asset within the time period; or (b) the removal of the personal data from the data asset in response to identifying an occurrence of the triggering event.

According to various aspects described herein, the method may include: (1) generating, by the computing hardware, a graphical user interface based on the first portion of the personal data by configuring a control element configured to generate a request to remove the first portion of the personal data from the data asset and a presentation element configured for presenting an indication of the first portion of the personal data; (2) transmitting, by the computing hardware, an instruction to an application executing on a user device causing the application to present the graphical user interface on the user device; and (3) facilitating, by the computing hardware, the removal of the first portion of the personal data from the data asset in response to a selection of the control element. According to particular aspects, the method comprises: (1) receiving, by the computing hardware, an indication of a new processing activity associated with the data asset; and (2) responsive to the indication of the new processing activity, modifying, by the computing hardware, the data model to include mapping data identifying an association between the new processing activity and a piece of personal data on the data asset. In various aspects, facilitating the removal of the first portion of the personal data comprises modifying metadata associated with the first portion of the personal data to indicate that the first portion of the personal data is orphaned data.

A system, according to various aspects, comprises: (1) processing hardware; (2) computer memory communicatively coupled to the processing hardware; and (3) non-transitory computer-readable medium communicatively coupled to the processing hardware, and storing computer-executable instructions. According to any aspect descried herein, the processing hardware is configured for executing the computer-executable instructions and thereby performing operations comprising: (1) accessing a data asset; (2) scanning the data asset to identify personal data stored on the data asset and processing activities that utilize the data asset to generate a catalog of the processing activities and the personal data; (3) scanning the data asset based on the generated catalog to identify a first portion of the personal data that is not associated with the processing activities; and (4) removing the first portion of the personal data from the data asset. According to particular aspects, the operations further comprise: (1) generating a graphical user interface based on the first portion of the personal data by configuring a control element configured to generate a request to remove the portion of the personal data from the data asset and a presentation element configured for presenting an indication of the portion of the personal data; (2) transmitting an instruction to an application executing on a user device causing the application to present the graphical user interface on the user device; and (3) removing the first portion of the personal data from the data asset in response to a selection of the control element. According to other aspects, the operations further comprise: (1) scanning the data asset based on the generated catalog to identify a second portion of the personal data that is associated with a terminated processing activity of the processing activities; and (2) removing the second portion of the personal data from the data asset. In some aspects, the operations further comprise: (1) accessing a data retention parameter for the data asset, the data retention parameter defining a time period for the removal of the first portion of the personal data; and (2) removing the first portion of the personal data from the data asset according to the data retention parameter by removing the first portion of the personal data after the time period. In particular aspects, the operations further comprise generating a data model that maps an association between each piece of the personal data stored on the data asset and a respective processing activity of the processing activities. In still other aspects, the operations further comprise: analyzing the data model to identify a second portion of the personal data that is associated with a terminated processing activity of the processing activities; and facilitating removal of the second portion of the personal data from the data asset.

A method, according to various aspects, comprises: (1) accessing, by computing hardware, a data model that maps an association between personal data stored on a data asset and respective processing activities undertaken by an entity; (2) analyzing, by the computing hardware, the data model to identify a portion of the personal data that is not associated with an active processing activity of the processing activities; and (3) facilitating removal, by the computing hardware, of the portion of the personal data from the data asset. In some aspects, the portion of the personal data comprises at least one of: (1) data this is not associated with any of the processing activities; and (2) data that is associated with a terminated processing activity of the processing activities. In particular aspects, the method further comprises: (1) generating, by the computing hardware, a graphical user interface based on the portion of the personal data by configuring a control element configured to generate a request to remove the portion of the personal data from the data asset and a presentation element configured for presenting an indication of the portion of the personal data; (2) transmitting, by the computing hardware, an instruction to an application executing on a user device causing the application to present the graphical user interface on the user device; and (3) facilitating, by the computing hardware, the removal of the portion of the personal data from the data asset in response to a selection of the control element.

The method, according to yet another aspect, includes: (1) scanning, by the computing hardware, the data asset to identify the personal data stored on the data asset and the processing activities undertaken by the entity that utilize the data asset to generate a catalog of the personal data; and (2) scanning, by the computing hardware, the data asset based on the generated catalog to generate the data model. According to various aspects, facilitating the removal of the portion of the personal data comprises modifying metadata associated with the portion of the personal data to indicate that the portion of the personal data is orphaned data.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a data subject access request fulfillment system are described below. In the course of this description, reference will be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 depicts a data subject request processing and fulfillment system according to particular embodiments.

FIG. 2A is a schematic diagram of a computer (such as the data model generation server 110, or data model population server 120 of FIG. 1 ) that is suitable for use in various embodiments of the data subject request processing and fulfillment system shown in FIG. 1 .

FIG. 2B is a flow chart depicting exemplary steps executed by a Data Subject Access Request Routing Module according to a particular embodiment

FIGS. 3-43 are computer screen shots that demonstrate the operation of various embodiments.

FIGS. 44-49 depict various exemplary screen displays and user interfaces that a user of various embodiments of the system may encounter (FIGS. 47 and 48 collectively show four different views of a Data Subject Request Queue).

FIG. 50 is a flowchart showing an example of processes performed by an Orphaned Data Action Module 5000 according to various embodiments.

FIG. 51 is a flowchart showing an example of processes performed by a Personal Data Deletion and Testing Module 5100 according to various embodiments.

FIG. 52 is a flowchart showing an example of processes performed by a Data Risk Remediation Module 5200 according to various embodiments.

FIG. 53 is a flowchart showing an example of processes performed by a Central Consent Module 5300 according to various embodiments.

FIG. 54 is a flowchart showing an example of processes performed by a Data Transfer Risk Identification Module 5400 according to various embodiments.

FIG. 55 is a is a flowchart showing an example of a process performed by an Automated Classification Module 5500 according to particular embodiments.

FIG. 56 is a screenshot of a document from which the system described herein may be configured to automatically classify personal information.

FIG. 57 depicts a visual representation of a plurality of objects that the system may create for each particular label identified in a document.

FIGS. 58-60 depict a visual representation of the system creating a classification and categorization of objects using contextual information from the document.

FIG. 61 depicts a visual representation of the system mapping values into an object structure according to the classification and categorization created as shown in FIGS. 57-59 .

FIG. 62 depicts a visual representation of the mapped results of an automatic classification of personal information in a document described herein.

DETAILED DESCRIPTION

Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings. It should be understood that the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

Overview

Ticket management systems, according to various embodiments, are adapted to receive data subject access requests (DSAR's) from particular data subjects, and to facilitate the timely processing of valid DSAR's by an appropriate respondent. In particular embodiments, the ticket management system receives DSAR's via one or more webforms that each may, for example, respectively be accessed via an appropriate link/button on a respective web page. In other embodiments, the system may receive DSAR's through any other suitable mechanism, such as via a computer software application (e.g., a messaging application such as Slack, Twitter), via a chat bot, via generic API input from another system, or through entry by a representative who may receive the information, for example, via suitable paper forms or over the phone.

The ticket management system may include a webform creation tool that is adapted to allow a user to create customized webforms for receiving DSAR's from various different data subject types and for routing the requests to appropriate individuals for processing. The webform creation tool may, for example, allow the user to specify the language that the form will be displayed in, what particular information is to be requested from the data subject and/or provided by the data subject, who any DSAR's that are received via the webform will be routed to, etc. In particular embodiments, after the user completes their design of the webform, the webform creation tool generates code for the webform that may be cut and then pasted into a particular web page.

The system may be further adapted to facilitate processing of DSAR's that are received via the webforms, or any other suitable mechanism. For example, the ticket management system may be adapted to execute one or more of the following steps for each particular DSAR received via the webforms (or other suitable mechanism) described above: (1) before processing the DSAR, confirm that the DSAR was actually submitted by the particular data subject of the DSAR (or, for example, by an individual authorized to make the DSAR on the data subject's behalf, such as a parent, guardian, power-of-attorney holder, etc.)—any suitable method may be used to confirm the identity of the entity/individual submitting the DSAR—for example, if the system receives the DSAR via a third-party computer system, the system may validate authentication via API secret, or by requiring a copy of one or more particular legal documents (e.g., a particular contract between two particular entities)—the system may validate the identity of an individual by, for example, requiring the individual (e.g., data subject) to provide particular account credentials, by requiring the individual to provide particular out-of-wallet information, through biometric scanning of the individual (e.g., finger or retinal scan), or via any other suitable identity verification technique; (2) if the DSAR was not submitted by the particular data subject, deny the request; (3) if the DSAR was submitted by the particular data subject, advance the processing of the DSAR; (4) route the DSAR to the correct individual(s) or groups internally for handling; (5) facilitate the assignment of the DSAR to one or more other individuals for handling of one or more portions of the DSAR; (6) facilitate the suspension of processing of the data subject's data by the organization; and/or (7) change the policy according to which the data subject's personal data is retained and/or processed by the system. In particular embodiments, the system may perform any one or more of the above steps automatically. The system then generates a receipt for the DSAR request that the user can use as a transactional record of their submitted request.

In particular embodiments, the ticket management system may be adapted to generate a graphical user interface (e.g., a DSAR request-processing dashboard) that is adapted to allow a user (e.g., a privacy officer of an organization that is receiving the DSAR) to monitor the progress of any of the DSAR requests. The GUI interface may display, for each DSAR, for example, an indication of how much time is left (e.g., quantified in days and/or hours) before a legal and/or internal deadline to fulfill the request. The system may also display, for each DSAR, a respective user-selectable indicium that, when selected, may facilitate one or more of the following: (1) verification of the request; (2) assignment of the request to another individual; (3) requesting an extension to fulfill the request; (4) rejection of the request; or (5) suspension of the request.

As noted immediately above, and elsewhere in this application, in particular embodiments, any one or more of the above steps may be executed by the system automatically. As a particular example, the system may be adapted to automatically verify the identity of the DSAR requestor and then automatically fulfill the DSAR request by, for example, obtaining the requested information via a suitable data model and communicating the information to the requestor. As another particular example, the system may be configured to automatically route the DSAR to the correct individual for handling based at least in part on one or more pieces of information provided (e.g., in the webform).

In various embodiments, the system may be adapted to prioritize the processing of DSAR's based on metadata about the data subject of the DSAR. For example, the system may be adapted for: (1) in response to receiving a DSAR, obtaining metadata regarding the data subject; (2) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (3) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.

Examples of metadata that may be used to determine whether to adjust the priority of a particular DSAR include: (1) the type of request; (2) the location from which the request is being made; (3) the country of residency of the data subject and, for example, that county's tolerance for enforcing DSAR violations; (4) current sensitivities to world events; (5) a status of the requestor (e.g., especially loyal customer); or (6) any other suitable metadata.

In particular embodiments, any entity (e.g., organization, company, etc.) that collects, stores, processes, etc. personal data may require one or more of: (1) consent from a data subject from whom the personal data is collected and/or processed; and/or (2) a lawful basis for the collection and/or processing of the personal data. In various embodiments, the entity may be required to, for example, demonstrate that a data subject has freely given specific, informed, and unambiguous indication of the data subject's agreement to the processing of his or her personal data for one or more specific purposes (e.g., in the form of a statement or clear affirmative action). As such, in particular embodiments, an organization may be required to demonstrate a lawful basis for each piece of personal data that the organization has collected, processed, and/or stored. In particular, each piece of personal data that an organization or entity has a lawful basis to collect and process may be tied to a particular processing activity undertaken by the organization or entity.

A particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, because of the number of processing activities that an organization may undertake, and the amount of data collected as part of those processing activities over time, one or more data systems associated with an entity or organization may store or continue to store data that is not associated with any particular processing activity (e.g., any particular current processing activity). Under various legal and industry standards related to the collection and storage of personal data, the organization or entity may not have or may no longer have a legal basis to continue to store the data. As such, organizations and entities may require improved systems and methods to identify such orphaned data, and take corrective action, if necessary (e.g., to ensure that the organization may not be in violation of one or more legal or industry regulations).

In various embodiments, an orphaned personal data identification system may be configured to generate a data model (e.g., one or more data models) that maps one or more relationships between and/or among a plurality of data assets utilized by a corporation or other entity (e.g., individual, organization, etc.) in the context, for example, of one or more business processes or processing activities. In particular embodiments, the system is configured to generate and populate a data model substantially on the fly (e.g., as the system receives new data associated with particular processing activities). In still other embodiments, the system is configured to generate and populate a data model based at least in part on existing information stored by the system (e.g., in one or more data assets), for example, using one or more suitable scanning techniques. In still other embodiments, the system is configured to access an existing data model that maps personal data stored by one or more organization systems to particular associated processing activities.

In various embodiments, the system may analyze the data model to identify personal data that has been collected and stored using one or more computer systems operated and/or utilized by a particular organization where the personal data is not currently being used as part of any privacy campaigns, processing activities, etc. undertaken by the particular organization. This data may be described as orphaned data. In some circumstances, the particular organization may be exposed to an increased risk that the data may be accessed by a third party (e.g., cybercrime) or that the particular organization may not be in compliance with one or more legal or industry requirements related to the collection, storage, and/or processing of this orphaned data.

Additionally, in some implementations, in response to the termination of a particular privacy campaign, processing activity, (e.g., manually or automatically), the system may be configured to analyze the data model to determine whether any of the personal data that has been collected and stored by the particular organization is now orphaned data (e.g., whether any personal data collected and stored as part of the now-terminated privacy campaign is being utilized by any other processing activity, has some other legal basis for its continued storage, etc.).

In additional implementations in response to determining that a particular privacy campaign, processing activity, etc. has not been utilized for a period of time (e.g., a day, month, year), the system may be configured to terminate the particular privacy campaign, processing activity, etc. or prompt one or more individuals associated with the particular organization to indicate whether the particular privacy campaign, processing activity, etc. should be terminated or otherwise discontinued.

For example, a particular processing activity may include transmission of a periodic advertising e-mail for a particular company (e.g., a hardware store). As part of the processing activity, the particular company may have collected and stored e-mail addresses for customers that elected to receive (e.g., consented to the receipt of) promotional e-mails. In response to determining that the particular company has not sent out any promotional e-mails for at least a particular amount of time (e.g., for at least a particular number of months), the system may be configured to: (1) automatically terminate the processing activity; (2) identify any of the personal data collected as part of the processing activity that is now orphaned data (e.g., the e-mail addresses); and (3) automatically delete the identified orphaned data. The processing activity may have ended for any suitable reason (e.g., because the promotion that drove the periodic e-mails has ended). As may be understood in light of this disclosure, because the particular organization no longer has a valid basis for continuing to store the e-mail addresses of the customers once the e-mail addresses are no longer being used to send promotional e-mails, the organization may wish to substantially automate the removal of personal data stored in its computer systems that may place the organization in violation of one or more personal data storage rules or regulations.

When the particular privacy campaign, processing activity, etc. is terminated or otherwise discontinued, the system may use the data model to determine if any of the associated personal data that has been collected and stored by the particular organization is now orphaned data.

In various embodiments, the system may be configured to identify orphaned data of a particular organization and automatically delete the data. In some implementations, in response to identifying the orphaned data, the system may present the data to one or more individuals associated with the particular organization (e.g., a privacy officer) and prompt the one or more individuals to indicate why the orphaned data is being stored by the particular organization. The system may then enable the individual to provide one or more valid reasons for the data's continued storage, or enable the one or more individuals to delete the particular orphaned data. In some embodiments, the system may automatically delete the orphaned data if, for example: (1) in response to determining that a reason provided by the individual is not a sufficient basis for the continued storage of the personal data; (2) the individual does not respond to the request to provide one or more valid reasons in a timely manner; (3) etc. In some embodiments, one or more other individuals may review the response provided indicating why the orphaned data is being stored, and in some embodiments, the one or more other individuals can delete the particular orphaned data.

In various embodiments, the system may be configured to review the data collection policy (e.g., how data is acquired, security of data storage, who can access the data, etc.) for the particular organization as well as one or more data retention metrics for the organization. For example, the one or more data retention metrics may include how much personal data is being collected, how long the data is held, how many privacy campaigns or other processes are using the personal data, etc. Additionally, the system may compare the particular organization's data collection policy and data retention metrics to the industry standards (e.g., in a particular field, based on a company size, etc.). In various embodiments, the system may be configured to generate a report that includes the comparison and provide the report to the particular organization (e.g., in electronic format).

In particular embodiments, the system may be configured advise the particular organization to delete data and identify particular data that should be deleted. In some embodiments, the system may automatically delete particular data (e.g., orphaned data). Further, the system may be configured to calculate and provide a risk score for particular data or the organization's data collection policy overall. In particular embodiments, the system may be configured to calculate the risk score based on the combinations of personal data elements in the data inventory of the organization (e.g., where an individual's phone number is stored in one location and their mailing address is stored in another location), and as such the risk may be increased because the additional pieces of personal information can make the stored data more sensitive.

In particular embodiments, any entity (e.g., organization, company, etc.) that collects, stores, processes, etc. personal data may require one or more of: (1) consent from a data subject from whom the personal data is collected and/or processed; and/or (2) a lawful basis for the collection and/or processing of the personal data. In various embodiments, the entity may be required to, for example, demonstrate that a data subject has freely given specific, informed, and unambiguous indication of the data subject's agreement to the processing of his or her personal data for one or more specific purposes (e.g., in the form of a statement or clear affirmative action). As such, in particular embodiments, an organization may be required to demonstrate a lawful basis for each piece of personal data that the organization has collected, processed, and/or stored. In particular, each piece of personal data that an organization or entity has a lawful basis to collect and process may be tied to a particular processing activity undertaken by the organization or entity.

A particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, because of the number of processing activities that an organization may undertake, and the amount of data collected as part of those processing activities over time, one or more data systems associated with an entity or organization may store or continue to store data that is not associated with any particular processing activity (e.g., any particular current processing activity). Under various legal and industry standards related to the collection and storage of personal data, such data may not have or may no longer have a legal basis for the organization or entity to continue to store the data. As such, organizations and entities may require improved systems and methods to maintain an inventory of data assets utilized to process and/or store personal data for which a data subject has provided consent for such storage and/or processing.

In various embodiments, the system is configured to provide a third-party data repository system to facilitate the receipt and centralized storage of personal data for each of a plurality of respective data subjects, as described herein. Additionally, the third-party data repository system is configured to interface with a centralized consent receipt management system.

In particular embodiments, the system may be configured to use one or more website scanning tools to, for example, identify a form (e.g., a webform) and locate a data asset where the input data is transmitted (e.g., Salesforce). Additionally, the system may be configured to add the data asset to the third-party data repository (e.g., and/or data map/data inventory) with a link to the form. In response to a user inputting form data (e.g., name, address, credit card information, etc.) of the form and submitting the form, the system may, based on the link to the form, create a unique subject identifier to submit to the third-party data repository and, along with the form data, to the data asset. Further, the system may use the unique subject identifier of a user to access and update each of the data assets of the particular organization. For example, in response to a user submitting a data subject access request to delete the user's personal data that the particular organization has stored, the system may use the unique subject identifier of the user to access and delete the user's personal data stored in all of the data assets (e.g., Salesforce, Eloqua, Marketo, etc.) utilized by the particular organization.

The system may, for example: (1) generate, for each of a plurality of data subjects, a respective unique subject identifier in response to submission, by each data subject, of a particular form; (2) maintain a database of each respective unique subject identifier; and (3) electronically link each respective unique subject identifier to each of: (A) a form initially submitted by the user; and (B) one or more data assets that utilize data received from the data subject via the form.

In various embodiments, the system may be configured to, for example: (1) identify a form used to collect one or more pieces of personal data, (2) determine a data asset of a plurality of data assets of the organization where input data of the form is transmitted, (3) add the data asset to the third-party data repository with an electronic link to the form, (4) in response to a user submitting the form, create a unique subject identifier to submit to the third-party data repository and, along with the form data provided by the user in the form, to the data asset, (5) submit the unique subject identifier and the form data provided by the user in the form to the third-party data repository and the data asset, and (6) digitally store the unique subject identifier and the form data provided by the user in the form in the third-party data repository and the data asset.

In some embodiments, the system may be further configured to, for example: (1) receive a data subject access request from the user (e.g., a data subject rights' request, a data subject deletion request, etc.), (2) access the third-party data repository to identify the unique subject identifier of the user, (3) determine which data assets of the plurality of data assets of the organization include the unique subject identifier, (4) access personal data of the user stored in each of the data assets of the plurality of data assets of the organization that include the unique subject identifier, and (5) take one or more actions based on the data subject access request (e.g., delete the accessed personal data in response to a data subject deletion request).

Various privacy and security policies (e.g., such as the European Union's General Data Protection Regulation, and other such policies) may provide data subjects (e.g., individuals, organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an entity. In particular, under various privacy and security policies, a data subject may be entitled to a right to erasure of any personal data associated with that data subject that has been at least temporarily stored by the entity (e.g., a right to be forgotten). In various embodiments, under the right to erasure, an entity (e.g., a data controller on behalf of another organization) may be obligated to erase personal data without undue delay under one or more of the following conditions: (1) the personal data is no longer necessary in relation to a purpose for which the data was originally collected or otherwise processed; (2) the data subject has withdrawn consent on which the processing of the personal data is based (e.g., and there is no other legal grounds for such processing); (3) the personal data has been unlawfully processed; (4) the data subject has objected to the processing and there is no overriding legitimate grounds for the processing of the data by the entity; and/or (5) for any other suitable reason or under any other suitable conditions.

In particular embodiments, a personal data deletion system may be configured to: (1) at least partially automatically identify and delete personal data that an entity is required to erase under one or more of the conditions discussed above; and (2) perform one or more data tests after the deletion to confirm that the system has, in fact, deleted any personal data associated with the data subject.

In particular embodiments, in response to a data subject submitting a request to delete their personal data from an entity's systems, the system may, for example: (1) automatically determine where the data subject's personal data is stored; and (2) in response to determining the location of the data (which may be on multiple computing systems), automatically facilitate the deletion of the data subject's personal data from the various systems (e.g., by automatically assigning a plurality of tasks to delete data across multiple business systems to effectively delete the data subject's personal data from the systems). In particular embodiments, the step of facilitating the deletion may comprise, for example: (1) overwriting the data in memory; (2) marking the data for overwrite; (2) marking the data as free (e.g., deleting a directory entry associated with the data); and/or (3) using any other suitable technique for deleting the personal data. In particular embodiments, as part of this process, the system may use any suitable data modelling technique to efficiently determine where all of the data subject's personal data is stored.

In various embodiments, the system may be configured to store (e.g., in memory) an indication that the data subject has requested to delete any of their personal data stored by the entity has been processed. Under various legal and industry policies/standards, the entity may have a certain period of time (e.g., a number of days) in order to comply with the one or more requirements related to the deletion or removal of personal data in response to receiving a request from the data subject or in response to identifying one or more of the conditions requiring deletion discussed above. In response to the receiving of an indication that the deletion request for the data subject's personal data has been processed or the certain period of time (described above) has passed, the system may be configured to perform a data test to confirm the deletion of the data subject's personal data.

In particular embodiments, when performing the data test, the system may be configured to provide an interaction request to the entity on behalf of the data subject. In particular embodiments, the interaction request may include, for example, a request for one or more pieces of data associated with the data subject (e.g., account information, etc.). In various embodiments, the interaction request is a request to contact the data subject (e.g., for any suitable reason). The system may, for example, be configured to substantially automatically complete a contact-request form (e.g., a webform made available by the entity) on behalf of the data subject. In various embodiments, when automatically completing the form on behalf of the data subject, the system may be configured to only provide identifying data, but not provide any contact data. In response to submitting the interaction request (e.g., submitting the webform), the system may be configured to determine whether the one or more computers systems have generated and/or transmitted a response to the data subject. The system may be configured to determine whether the one or more computers systems have generated and/or transmitted the response to the data subject by, for example, analyzing one or more computer systems associated with the entity to determine whether the one or more computer systems have generated a communication to the data subject (e.g., automatically) for transmission to an e-mail address or other contact method associated with the data subject, generated an action-item for an individual to contact the data subject at a particular contact number, etc.

In response to determining that the one or more computer systems has generated and/or transmitted the response to the data subject, the system may be configured to determine that the one or more computer systems has not complied with the data subject's request for deletion of their personal data from the one or more computers systems associated with the entity. In response, the system may generate an indication that the one or more computer systems has not complied with the data subject's request for deletion of their personal data from the one or more computers systems have, and store the indication in computer memory.

To perform the data test, for example, the system may be configured to: (1) access (e.g., manually or automatically) a form for the entity (e.g., a web-based “Contact Us” form); (2) input a unique identifier associated with the data subject (e.g., a full name or customer ID number) without providing contact information for the data subject (e.g., mailing address, phone number, email address, etc.); and (3) input a request, within the form, for the entity to contact the data subject to provide information associated with the data subject (e.g., the data subject's account balance with the entity). In response to submitting the form to the entity, the system may be configured to determine whether the data subject is contacted (e.g., via a phone call or email) by the one or more computer systems (e.g., automatically). In response to determining that the data subject has been contacted following submission of the form, the system may determine that the one or more computer systems have not fully deleted the data subject's personal data (e.g., because the one or more computer systems must still be storing contact information for the data subject in at least one location).

In particular embodiments, the system is configured to generate one or more test profiles for one or more test data subjects. For each of the one or more test data subjects, the system may be configured to generate and store test profile data such as, for example: (1) name; (2) address; (3) telephone number; (4) e-mail address; (5) social security number; (6) information associated with one or more credit accounts (e.g., credit card numbers); (7) banking information; (8) location data; (9) internet search history; (10) non-credit account data; and/or (11) any other suitable test data. The system may then be configured to at least initially consent to processing or collection of personal data for the one or more test data subjects by the entity. The system may then request deletion, by the entity, of any personal data associated with a particular test data subject. In response to requesting the deletion of data for the particular test data subject, the system may then take one or more actions using the test profile data associated with the particular test data subjects in order to confirm that the one or more computers systems have, in fact, deleted the test data subject's personal data (e.g., any suitable action described herein). The system may, for example, be configured to: (1) initiate a contact request on behalf of the test data subject; (2) attempt to login to one or more user accounts that the system had created for the particular test data subject; and/or (3) take any other action, the effect of which could indicate a lack of complete deletion of the test data subject's personal data.

In response to determining that the one or more computer systems have not fully deleted a data subject's (or test data subject's) personal data, the system may then be configured, in particular embodiments, to: (1) flag the data subject's personal data for follow up by one or more privacy officers to investigate the lack of deletion; (2) perform one or more scans of one or more computing systems associated with the entity to identify any residual personal data that may be associated with the data subject; (3) generate a report indicating the lack of complete deletion; and/or (4) take any other suitable action to flag for follow-up the data subject, personal data, initial request to be forgotten, etc.

The system may, for example, be configured to test to ensure the data has been deleted by: (1) submitting a unique token of data through a form to a system (e.g., mark to); (2) in response to passage of an expected data retention time, test the system by calling into the system after the passage of the data retention time to search for the unique token. In response to finding the unique token, the system may be configured to determine that the data has not been properly deleted.

In various embodiments, a system may be configured to substantially automatically determine whether to take one or more actions in response to one or more identified risk triggers. For example, an identified risk trigger may be that a data asset for an organization is hosted in only one particular location thereby increasing the scope of risk if the location were infiltrated (e.g., via cybercrime). In particular embodiments, the system is configured to substantially automatically perform one or more steps related to the analysis of and response to the one or more potential risk triggers discussed above. For example, the system may substantially automatically determine a relevance of a risk posed by (e.g., a risk level) the one or more potential risk triggers based at least in part on one or more previously-determined responses to similar risk triggers. This may include, for example, one or more previously determined responses for the particular entity that has identified the current risk trigger, one or more similarly situated entities, or any other suitable entity or potential trigger.

In particular embodiments, the system may, for example, be configured to: (1) receive risk remediation data for a plurality of identified risk triggers from a plurality of different entities; (2) analyze the risk remediation data to determine a pattern in assigned risk levels and determined response to particular risk triggers; and (3) develop a model based on the risk remediation data for use in facilitating an automatic assessment of and/or response to future identified risk triggers.

In some embodiments, when a change or update is made to one or more processing activities and/or data assets (e.g., a database associated with a particular organization), the system may use data modeling techniques to update the risk remediation data for use in facilitating an automatic assessment of and/or response to future identified risk triggers. In various embodiments, when a privacy campaign, processing activity, etc. of the particular organization is modified (e.g., add, remove, or update particular information), then the system may use the risk remediation data for use in facilitating an automatic assessment of and/or response to future identified risk triggers.

In particular embodiments, the system may, for example, be configured to: (1) access risk remediation data for an entity that identifies one or more suitable actions to remediate a risk in response to identifying one or more data assets of the entity that may be affected by one or more potential risk triggers; (2) receive an indication of an update to the one or more data assets; (3) identify one or more potential updated risk triggers for an entity; (4) assess and analyze the one or more potential updated risk triggers to determine a relevance of a risk posed to the entity by the one or more potential updated risk triggers; (5) use one or more data modeling techniques to identify one or more data assets associated with the entity that may be affected by the risk; and (6) update the risk remediation data to include the one or more actions to remediate the risk in response to identifying the one or more potential updated risk triggers.

In any embodiment described herein, an automated classification system may be configured to substantially automatically classify one or more pieces of personal information in one or more documents (e.g., one or more text-based documents, one or more spreadsheets, one or more PDFs, one or more webpages, etc.). In particular embodiments, the system may be implemented in the context of any suitable privacy compliance system, which may, for example, be configured to calculate and assign a sensitivity score to a particular document based at least in part on one or more determined categories of personal information (e.g., personal data) identified in the one or more documents. As understood in the art, the storage of particular types of personal information may be governed by one or more government or industry regulations. As such, it may be desirable to implement one or more automated measures to automatically classify personal information from stored documents (e.g., to determine whether such documents may require particular security measures, storage techniques, handling, whether the documents should be destroyed, etc.).

Exemplary Technical Platforms

As will be appreciated by one skilled in the relevant field, the present invention may be, for example, embodied as a computer system, a method, or a computer program product. Accordingly, various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, particular embodiments may take the form of a computer program product stored on a computer-readable storage medium having computer-readable instructions (e.g., software) embodied in the storage medium. Various embodiments may take the form of web-implemented computer software. Any suitable computer-readable storage medium may be utilized including, for example, hard disks, compact disks, DVDs, optical storage devices, and/or magnetic storage devices.

Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatuses (e.g., systems), and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by a computer executing computer program instructions. These computer program instructions may be loaded onto a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus to create means for implementing the functions specified in the flowchart block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner such that the instructions stored in the computer-readable memory produce an article of manufacture that is configured for implementing the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of mechanisms for performing the specified functions, combinations of steps for performing the specified functions, and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and other hardware executing appropriate computer instructions.

Example System Architecture

FIG. 1 is a block diagram of a data subject access request processing and fulfillment system 100 according to a particular embodiment. In various embodiments, the data subject access request processing and fulfillment system is part of a privacy compliance system (also referred to as a privacy management system), or other system, which may, for example, be associated with a particular organization and be configured to aid in compliance with one or more legal or industry regulations related to the collection and storage of personal data.

As may be understood from FIG. 1 , the data subject access request processing and fulfillment system 100 includes one or more computer networks 115, a Data Model Generation Server 110, a Data Model Population Server 120, an Intelligent Identity Scanning Server 130 (which may automatically validate a DSAR requestor's identity), One or More Databases 140 or other data structures, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), and One or More Third Party Servers 160. In particular embodiments, the one or more computer networks 115 facilitate communication between the Data Model Generation Server 110, Data Model Population Server 120, Intelligent Identity Scanning/Verification Server 130, One or More Databases 140, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), One or More Third Party Servers 160, and DSAR Processing and Fulfillment Server 170. Although in the embodiment shown in FIG. 1 , the Data Model Generation Server 110, Data Model Population Server 120, Intelligent Identity Scanning Server 130, One or More Databases 140, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), and One or More Third Party Servers 160, and DSAR Processing and Fulfillment Server 170 are shown as separate servers, it should be understood that in other embodiments, the functionality of one or more of these servers and/or computing devices may, in different embodiments, be executed by a larger or smaller number of local servers, one or more cloud-based servers, or any other suitable configuration of computers.

The one or more computer networks 115 may include any of a variety of types of wired or wireless computer networks such as the Internet, a private intranet, a public switch telephone network (PSTN), or any other type of network. The communication link between the DSAR Processing and Fulfillment Server 170 and the One or More Remote Computing Devices 150 may be, for example, implemented via a Local Area Network (LAN) or via the Internet. In other embodiments, the One or More Databases 140 may be stored either fully or partially on any suitable server or combination of servers described herein.

FIG. 2A illustrates a diagrammatic representation of a computer 200 that can be used within the data subject access request processing and fulfillment system 100, for example, as a client computer (e.g., one or more remote computing devices 150 shown in FIG. 1 ), or as a server computer (e.g., Data Model Generation Server 110 shown in FIG. 1 ). In particular embodiments, the computer 200 may be suitable for use as a computer within the context of the data subject access request processing and fulfillment system 100 that is configured for routing and/or processing DSAR requests and/or generating one or more data models used in automatically fulfilling those requests.

In particular embodiments, the computer 200 may be connected (e.g., networked) to other computers in a LAN, an intranet, an extranet, and/or the Internet. As noted above, the computer 200 may operate in the capacity of a server or a client computer in a client-server network environment, or as a peer computer in a peer-to-peer (or distributed) network environment. The Computer 200 may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any other computer capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that computer. Further, while only a single computer is illustrated, the term “computer” shall also be taken to include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

An exemplary computer 200 includes a processing device 202, a main memory 204 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), static memory 206 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 218, which communicate with each other via a bus 232.

The processing device 202 represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device 202 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device 202 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device 202 may be configured to execute processing logic 226 for performing various operations and steps discussed herein.

The computer 120 may further include a network interface device 208. The computer 200 also may include a video display unit 210 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 212 (e.g., a keyboard), a cursor control device 214 (e.g., a mouse), and a signal generation device 216 (e.g., a speaker).

The data storage device 218 may include a non-transitory computer-accessible storage medium 230 (also known as a non-transitory computer-readable storage medium or a non-transitory computer-readable medium) on which is stored one or more sets of instructions (e.g., software instructions 222) embodying any one or more of the methodologies or functions described herein. The software instructions 222 may also reside, completely or at least partially, within main memory 204 and/or within processing device 202 during execution thereof by computer 200—main memory 204 and processing device 202 also constituting computer-accessible storage media. The software instructions 222 may further be transmitted or received over a network 115 via network interface device 208.

While the computer-accessible storage medium 230 is shown in an exemplary embodiment to be a single medium, the term “computer-accessible storage medium” should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The terms “computer-accessible storage medium”, “computer-readable medium”, and like terms should also be understood to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the computer and that cause the computer to perform any one or more of the methodologies of the present invention. These terms should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc.

Systems for Managing Data Subject Access Requests

In various embodiments, the system may include a ticket management system and/or other systems for managing data subject access requests. In operation, the system may use one or more computer processors, which are operatively coupled to memory, to execute one or more software modules (which may be included in the Instructions 222 referenced above) such as: (1) a DSAR Request Routing Module 1000; and (4) a DSAR Prioritization Module. An overview of the functionality and operation of each of these modules is provided below.

Data Subject Access Request Routing Module 1000

As shown in FIG. 2B, a Data Subject Access Request Routing Module 1000, according to particular embodiments, is adapted for executing the steps of: (1) at Step 1050, presenting, by at least one computer processor, a first webform on a first website, the first webform being adapted to receive data subject access requests and to route the requests to a first designated individual (e.g., an individual who is associated with a first sub-organization of a particular organization—e.g., an employee of the first sub-organization) for processing (in various embodiments, “presenting a webform on a website” may comprise, for example: (A) providing a button, link, or other selectable indicium on the website that, when selected, causes the system to display the webform, or (B) displaying the webform directly on the website); (2) at Step 1100 presenting, by at least one computer processor, a second webform on a second website, the second webform being adapted to receive data subject access requests and to route the requests to a second designated individual (e.g., an individual who is associated with a second sub-organization of a particular organization—e.g., an employee of the second sub-organization) for processing; (3) at Step 1150, receiving, by at least one computer processor, via the first webform, a first data subject access request; (4) at Step 1200, at least partially in response to the receiving the first data subject access request, automatically routing the first data subject access request to the first designated individual for handling; (5) at Step 1250, at least partially in response to the receiving the second data subject access request, automatically routing the second data subject access request to the second designated individual for handling; and (6) at Step 1300, communicating, via a single user interface, a status of both the first data subject access request and the second data subject access request.

In particular embodiments: (1) the first website is a website of a first sub-organization of a particular parent organization; (2) the second website is a website of a second sub-organization of the particular parent organization; and (3) the computer-implemented method further comprises communicating, by at least one computer processor, via a single user interface, a status of each of said first data subject access request and said second data subject access request (e.g., to an employee of—e.g., privacy officer of—the parent organization). As discussed in more detail below, this single user interface may display an indication, for each respective one of the first and second data subject access requests, of a number of days remaining until a deadline for fulfilling the respective data subject access request.

In certain embodiments, the single user interface is adapted to facilitate the deletion or assignment of multiple data subject access requests to a particular individual for handling in response to a single command from a user (e.g., in response to a user first selecting multiple data subject access requests from the single user interface and then executing an assign command to assign each of the multiple requests to a particular individual for handling).

In particular embodiments, the system running the Data Subject Access Request Routing Module 1000, according to particular embodiments, may be adapted for, in response to receiving each data subject access request, generating an ID number (e.g., a transaction ID or suitable Authentication Token) for the first data subject access request, which may be used later, by the DSAR requestor, to access information related to the DSAR, such as personal information requested via the DSAR, the status of the DSAR request, etc. To facilitate this, the system may be adapted for receiving the ID number from an individual and, at least partially in response to receiving the ID number from the individual, providing the individual with information regarding status of the data subject access request and/or information previously requested via the data subject access request.

In particular embodiments, the system may be adapted to facilitate the processing of multiple different types of data subject access requests. For example, the system may be adapted to facilitate processing: (1) requests for all personal data that an organization is processing for the data subject (a copy of the personal data in a commonly used, machine-readable format); (2) requests for all such personal data to be deleted; (3) requests to update personal data that the organization is storing for the data subject; (4) requests to opt out of having the organization use the individual's personal information in one or more particular ways (e.g., per the organization's standard business practices), or otherwise change the way that the organization uses the individual's personal information; and/or (5) the filing of complaints.

In particular embodiments, the system may execute one or more steps (e.g., any suitable step or steps discussed herein) automatically. For example, the system may be adapted for: (1) receiving, from the first designated individual, a request to extend a deadline for satisfying the first data subject access request; (2) at least partially in response to receiving the extension request, automatically determining, by at least one processor, whether the requested extension complies with one or more applicable laws or internal policies; and (3) at least partially in response to determining that the requested extension complies with the one or more applicable laws or internal policies, automatically modifying the deadline, in memory, to extend the deadline according to the extension request. The system may be further adapted for, at least partially in response to determining that the requested extension does not comply with the one or more applicable laws or internal policies, automatically rejecting the extension request. In various embodiments, the system may also, or alternatively, be adapted for: (1) at least partially in response to determining that the requested extension does not comply with the one or more applicable laws or internal policies, automatically modifying the length of the requested extension to comply with the one or more applicable laws or internal policies; and (2) automatically modifying the deadline, in memory, to extend the deadline according to the extension request.

In various embodiments, the system may be adapted for: (1) automatically verifying an identity of a particular data subject access requestor placing the first data subject access request; (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically obtaining, from a particular data model, at least a portion of information requested in the first data subject access request; and (3) after obtaining the at least a portion of the requested information, displaying the obtained information to a user as part of a fulfillment of the first data subject access request. The information requested in the first data subject access request may, for example, comprise at least substantially all (e.g., most or all) of the information regarding the first data subject that is stored within the data model.

In various embodiments, the system is adapted for: (1) automatically verifying, by at least one computer processor, an identity of a particular data subject access requestor placing the first data subject access request; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically facilitating an update of personal data that an organization associated with the first webform is processing regarding the particular data subject access requestor.

Similarly, in particular embodiments, the system may be adapted for: (1) automatically verifying, by at least one computer processor, an identity of a particular data subject access requestor placing the first data subject access request; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically processing a request, made by the particular data subject access requestor, to opt out of having the organization use the particular data subject access requestor's personal information in one or more particular ways.

The system may, in various embodiments, be adapted for: (1) providing, by at least one computer processor, a webform creation tool that is adapted for receiving webform creation criteria from a particular user, the webform creation criteria comprising at least one criterion from a group consisting of: (A) a language that the form will be displayed in; (B) what information is to be requested from data subjects who use the webform to initiate a data subject access request; and (C) who any data subject access requests that are received via the webform will be routed to; and (2) executing the webform creation tool to create both the first webform and the second webform.

In light of the discussion above, although the Data Subject Access Request Routing Module 1000 is described as being adapted to, in various embodiments, route data subject access requests to particular individuals for handling, it should be understood that, in particular embodiments, this module may be adapted to process at least part of, or all of, particular data subject access requests automatically (e.g., without input from a human user). In such cases, the system may or may not route such automatically-processed requests to a designated individual for additional handling or monitoring. In particular embodiments, the system may automatically fulfill all or a portion of a particular DSAR request, automatically assign a transaction ID and/or authentication token to the automatically fulfilled transaction, and then display the completed DSAR transaction for display on a system dashboard associated with a particular responsible individual that would otherwise have been responsible for processing the DSAR request (e.g., an individual to whom the a webform receiving the DSAR would otherwise route DSAR requests). This may be helpful in allowing the human user to later track, and answer any questions about, the automatically-fulfilled DSAR request.

It should also be understood that, although the system is described, in various embodiments, as receiving DSAR requests via multiple webforms, each of which is located on a different website, the system may, in other embodiments, receive requests via only a single webform, or through any other suitable input mechanism other than a webform (e.g., through any suitable software application, request via SMS message, request via email, data transfer via a suitable API, etc.)

In various embodiments, the system may be adapted to access information needed to satisfy DSAR requests via one or more suitable data models. Such data models include those that are described in greater detail in U.S. patent application Ser. No. 15/996,208, filed Jun. 1, 2018, which, as noted above, is incorporated herein by reference. In various embodiments, the system is adapted to build and access such data models as described in this earlier-filed U.S. patent application.

As an example, in fulfilling a request to produce, modify, or delete, any of a data subject's personal information that is stored by a particular entity, the system may be adapted to access a suitable data model to identify any personal data of the data subject that is currently being stored in one or more computer systems associated with the particular entity. After using the data model to identify the data, the system may automatically process the data accordingly (e.g., by modifying or deleting it, and/or sharing it with the DSAR requestor).

DSAR Prioritization Module

A DSAR Prioritization Module, according to various embodiments, is adapted for (1) executing the steps of receiving a data subject access request; (2) at least partially in response to receiving the data subject access request, obtaining metadata regarding a data subject of the data subject access request; (3) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (4) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.

The operation of various embodiments of the various software modules above is described in greater detail below. It should be understood that the various steps described herein may be executed, by the system, in any suitable order and that various steps may be omitted, or other steps may be added in various embodiments.

Operation of Example Implementation

FIGS. 3-43 are screen shots that demonstrate the operation of a particular embodiment. FIGS. 3-6 show a graphical user interface (GUI) of an example webform construction tool. FIG. 3 shows a user working to design a webform called “Web_form_1”. As may be understood from the vertical menu shown on the left-hand side of the screen, the webform construction tool allows users to design a webform by: (1) specifying the details of the form (via the “Form Details” tab); (2) defining the fields that will be displayed on the webform (via the “Webform Fields” tab); (3) defining the styling of the webform (via the “Form Styling” tab); and (4) defining various settings associated with the webform (via the “Settings” tab). As shown in FIGS. 4-6 , the user may also specify text to be displayed on the webform (e.g., via a “Form Text” tab).

FIG. 4 shows that, by selecting the “Form Details” tab, the user may define which answers a requestor will be able to specify on the webform in response to prompts for information regarding what type of individual they are (customer, employee, etc.) and what type of request they are making via the webform. Example request types include: (1) a request for all personal data that an organization is processing for the data subject (a copy of the personal data in a commonly used, machine-readable format); (2) a request for all such personal data to be deleted; (3) a request to update personal data that the organization is storing for the data subject; (4) a request to opt out of having the organization use the individual's personal information in one or more particular ways (e.g., per the organization's standard business practices); (5) file a complaint; and/or (6) other.

FIG. 5 shows that, by selecting the “Settings” tab, the user may specify various system settings, such as whether Captcha will be used to verify that information is being entered by a human, rather than a computer.

FIG. 6 shows that, by selecting the Form Styling tab, the user may specify the styling of the webform. The styling may include, for example: (1) a header logo; (2) header height; (3) header color; (4) body text color; (5) body text size; (6) form label color; (7) button color; (8) button text color; (9) footer text color; (10) footer text size; and/or any other suitable styling related to the webform.

In other embodiments, the system is configured to enable a user to specify, when configuring a new webform, what individual at a particular organization (e.g., company) will be responsible for responding to requests made via the webform. The system may, for example, enable the user to define a specific default sub-organization (e.g., within the organization) responsible for responding to DSAR's submitted via the new webform. As such, the system may be configured to automatically route a new DSAR made via the new webform to the appropriate sub-organization for processing and fulfillment. In various embodiments, the system is configured to route one or more various portions of the DSAR to one or more different sub-organizations within the organization for handling.

In particular embodiments, the system may include any suitable logic for determining how the webform routes data subject access requests. For example, the system may be adapted to determine which organization or individual to route a particular data subject access request to based, at least in part, on one or more factors selected from a group consisting of: (1) the data subject's current location; (2) the data subject's country of residence; (3) the type of request being made; (4) the type of systems that contain (e.g., store and/or process) the user's personal data (e.g., in ADP, Salesforce, etc.); or any other suitable factor.

In particular embodiments, the system is configured to enable a user generating webforms to assign multiple webforms to multiple different respective suborganizations within an organization. For example, an organization called ACME, Inc. may have a website for each of a plurality of different brands (e.g., sub-organizations) under which ACME sells products (e.g., UNICORN Brand T-shirts, GRIPP Brand Jeans, etc.). As may be understood in light of this disclosure, each website for each of the particular brands may include an associated webform for submitting DSAR's (either a webform directly on the web site, or one that is accessible via a link on the website). Each respective webform may be configured to route a DSAR made via its associated brand website to a particular sub-organization and/or individuals within ACME for handling DSAR's related to the brand.

As noted above, after the user uses the webform construction tool to design a particular webform for use on a particular web page, the webform construction tool generates code (e.g., HTML code) that may be pasted into the particular web page to run the designed webform page. In particular embodiment, when pasted into the particular web page, the code generates a selectable button on the web page that, when selected, causes the system to display a suitable DSAR request webform.

FIG. 7 shows the privacy webpage of a company (e.g., the ACME corporation). As shown in this figure, a requestor may submit a DSAR by selecting a “Submit a Privacy Related Request” button on the web page.

FIG. 8 shows a webform that is displayed after a requestor selects the “Submit a Privacy Related Request” button on the privacy webpage of FIG. 7 . As may be understood from this figure, the requestor may complete the webform by specifying which type of user they are, and what type of request they are making. The webform also asks the requestor to provide enough personal information to confirm their identity (e.g., and fulfill the request). As shown in this figure, the system may prompt a user submitting a DSAR to provide information for the user such as, for example: (1) what type of requestor the user is (e.g., employee, customer, etc.); (2) what the request involves (e.g., requesting info, opting out, deleting data, updating data, etc.); (3) first name; (4) last name; (5) email address; (6) telephone number; (7) home address; (8) one or more other pieces of identifying information; and/or (9) one or more details associated with the request. FIG. 9 shows an example populated version of the webform.

As shown in FIG. 10 , after a requestor completes the webform and selects a “submit” indicia, the system displays a message to the requestor indicating that their DSAR has been successfully submitted. The system also displays a Request ID associated with the request. In response to the requestor successfully submitting the request, the system may also send an email (or other suitable communication) to the requestor confirming the request. An example of a suitable confirmation email is shown in FIG. 11 .

In various embodiments, the system includes a dashboard that may be used by various individuals within an organization (e.g., one or more privacy officers of an organization) to manage multiple DSAR requests. As discussed above, the dashboard may display DSAR's submitted, respectively, to a single organization, any of multiple different sub-organizations (divisions, departments, subsidiaries etc.) of a particular organization, and/or any of multiple independent organizations. For example, the dashboard may display a listing of DSAR's that were submitted from a parent organization and from the parent organization's U.S. and European subsidiaries. This may be advantageous, for example, because it may allow an organization to manage all DSAR requests of all of its sub-organizations (and/or other related organizations) centrally.

FIGS. 12-23, 25-27, 29-34, and 41-43 depict various example user-interface screens of a DSAR request-management dashboard. As may be understood from FIG. 12 , after an appropriate user (e.g., a privacy officer associated with a particular organization) logs into the system, the system may display a Data Subject Request Queue that may, for example, display a listing of all data subject access requests that the appropriate individual has been designated to process. As shown in FIG. 12 , each data subject access request may be represented by a respective row of information that includes: (1) an ID number for the request; (2) the name of the data subject who has submitted the request; (3) the status of the request; (4) the number of days that are left to respond to the request (e.g., according to applicable laws and/or internal procedures); (5) an indication as to whether the deadline to respond to the request has been extended; (6) a creation date of the request; (7) an indication of the type of requestor that submitted the request (customer, employee, etc.); (8) the name of the individual who has been assigned to process the request (e.g., the respondent). This screen may also include selectable “Edit” and “Filter” buttons that respectively facilitate acting on and filtering the various requests displayed on the page.

As shown in FIG. 13 , in response to a respondent selecting the edit button while a particular DSAR is highlighted, the system displays a dropdown menu allowing the respondent to select between taking the following actions: (1) verify the request; (2) assign the request to another individual; (3) request an extension; (4) reject the request; or (5) suspend the request.

FIGS. 14 and 15 show a message that the system displays to the respondent in response to the respondent selecting the “verify” option. As shown in this figure, the system prompts the respondent to indicate whether they are sure that they wish to authenticate the request. The system also presents an input field where the respondent can enter text to be displayed to the requestor along with a request for the requestor to provide information verifying that they are the data subject associated with the request. After the respondent populates the input field, they may submit the request by selecting a “Submit” button.

In particular embodiments, the input field may enable the respondent to provide one or more supporting reasons for a decision, by the respondent, to authenticate the request. The respondent may also upload one or more supporting documents (such as an attachment). The supporting documents or information may include, for example, one or more documents utilized in confirming the requestor's identity, etc.

In response to the respondent selecting the Submit button, the system changes the status of the request to “In Progress” and also changes the color of the request's status from orange to blue (or from any other suitable color to any different suitable color)—see FIG. 16 . The system also generates and sends a message (e.g., an electronic or paper message) to the requestor asking them to submit information verifying the request. The message may include the text that the respondent entered in the text box of FIG. 14 .

As shown in FIGS. 17-19 , in response to a respondent selecting the “Edit” button and then selecting the “Assign” indicia from the displayed dropdown menu, the system displays a Request Assignment interface that allows a respondent to indicate who the request should be assigned to. For example, the respondent may indicate that they will be handling the request, or assign the request to another suitable individual, who may, for example, then be designated as the respondent for the request. If the respondent assigns the request to another individual for handling, the respondent may also provide an email address or other correspondence information for the individual. The Request Assignment interface includes a comment box for allowing a respondent to add a message to the individual that the assignment will be assigned to regarding the assignment. In response to the respondent selecting the “Assign” button, the system assigns the request to the designated individual for handling. If the request has been assigned to another, designated individual, the system automatically generates and sends a message (e.g., an electronic message such as an email or SMS message) to the designated individual informing them of the assignment.

As shown in FIGS. 20-22 , in response to a respondent selecting the “Edit” button and then selecting the “Reject” indicia from the displayed dropdown menu, the system displays a Reject Request interface. This interface includes a comment box for allowing a respondent to add a message to the requestor as to why the request was rejected. In response to the respondent selecting the “Submit” button, the system changes the status of the request to “Rejected” and changes the color of the request's status indicator to red (See FIG. 23 ). The system may also automatically generate a message (e.g., an electronic or paper message) to the requestor notifying them that their request has been rejected and displaying the text that the respondent entered into the Reject Request interface of FIG. 22 . An example of such a message is shown in FIG. 24 .

As shown in FIGS. 25-26 , in response to a respondent selecting the “Edit” button and then selecting the “Request Extension” indicia from the displayed dropdown menu, the system displays a Request Extension interface. This includes a text box for allowing a user to indicate the number of days for which they would like to extend the current deadline for responding to the request. For example, the dialog box of FIG. 26 shows the respondent requesting that the current deadline be extended by 90 days. In response to the respondent entering a desired extension duration and selecting the “Submit” button, the system updates the deadline in the system's memory (e.g., in an appropriate data structure) to reflect the extension. For instance, in the example of FIG. 26 , the system extends the deadline to be 90 days later than the current deadline. As shown in FIG. 27 , the system also updates the “Days Left to Respond” field within the Data Subject Request Queue to reflect the extension (e.g., from 2 days from the current date to 92 days from the current date). As shown in FIG. 28 , the system may also generate an appropriate message (e.g., an electronic, such as an email, or a paper message) to the requestor indicating that the request has been delayed. This message may provide a reason for the delay and/or an anticipated updated completion date for the request.

In particular embodiments, the system may include logic for automatically determining whether a requested extension complies with one or more applicable laws or internal policies and, in response, either automatically grant or reject the requested extension. For example, if the maximum allowable time for replying to a particular request is 90 days under the controlling laws and the respondent requests an extension that would result in the fulfillment of the request 91 or more days from the date that the request was submitted, the system may automatically reject the extension request. In various embodiments, the system may also communicate, to the respondent (e.g., via a suitable electronic message or text display on a system user interface) an explanation as to why the extension request was denied, and/or a maximum amount of time (e.g., a maximum number of days) that the deadline may be extended under the applicable laws or policies. In various embodiments, if the system determines that the requested extension is permissible under the applicable laws and/or policies, the system may automatically grant the extension.

In other embodiments, the system may be configured to automatically modify a length of the requested extension to conform with one or more applicable laws and/or policies. For example, if the request was for a 90-day extension, but only a 60 day extension is available under the applicable laws or regulations, the system may automatically grant a 60-day extension rather than a 90 day extension. The system may be adapted to also automatically generate and transmit a suitable message (e.g., a suitable electronic or paper communication) notifying them of the fact that the extension was granted for a shorter, specified period of time than requested.

As shown in FIGS. 29-34 , a respondent may obtain additional details regarding a particular request by selecting (e.g., clicking on) the request on the Data Subject Request Queue screen. For example, FIG. 30 shows a Data Subject Request Details screen that the system displays in response to a respondent selecting the “Donald Blair” request on the user interface screen of FIG. 35 . As shown in FIG. 30 , the Data Subject Request Details screen shows all correspondence between the organization and the requesting individual regarding the selected data subject access request. As may be understood from FIG. 31 , when a respondent selects a particular correspondence (e.g., email), the system displays the correspondence to the respondent for review or other processing.

As shown in FIG. 32 , in various embodiments, the system may provide a selectable “Reply” indicia that allows the respondent to reply to particular correspondence from an individual. As may be understood from this figure, in response to the respondent selecting the “Reply” indicia, the system may display a dropdown menu of various standard replies. For example, the dropdown menu may provide the option of generating a reply to the requestor indicating that the request has been rejected, is pending, has been extended, or that the request has been completed.

As shown in FIG. 33 , in response to the respondent selecting “Reply as Completed”, the system may generate a draft email to the requestor explaining that the request has been completed. The respondent may then edit this email and send the edited correspondence (e.g., via email) to the requestor by selecting a “Send as Complete” indicia. As shown in FIG. 34 , the system may, in response, display an indicator adjacent the correspondence indicating that the correspondence included a reply indicating that the request was complete. This may be useful in allowing individuals to understand the contents of the correspondence without having to open it.

FIG. 35 shows an example email automatically generated by the system in response to the respondent selecting “Reply as Completed” on the screen shown in FIG. 32 . As shown in FIG. 35 , the correspondence may include a secure link that the requestor may select to access the data that was requested in the DSAR. In particular embodiments, the link is a link to a secure website, such as the website shown in FIG. 36 , that provides access to the requested data (e.g., by allowing a user to download a .pdf file, or other suitable file, that includes the requested data). As shown in FIG. 36 , the website may require multiple pieces of data to verify that the requestor is permitted to access the site. For example, in order to access the website, the requestor may be required to provide both the unique ID number of the request, and an authentication token, which the system may send to the user via email—See FIGS. 37 and 38 .

FIGS. 39-43 are computer screen shots that depict additional user interfaces according to various embodiments.

Additional Concepts

Intelligent Prioritization of DSAR's

In various embodiments, the system may be adapted to prioritize the processing of DSAR's based on metadata about the data subject of the DSAR. For example, the system may be adapted for: (1) in response to receiving a DSAR, obtaining metadata regarding the data subject; (2) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (3) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.

Examples of metadata that may be used to determine whether to adjust the priority of a particular DSAR include: (1) the type of request, (2) the location from which the request is being made, (3) current sensitivities to world events, (4) a status of the requestor (e.g., especially loyal customer), or (5) any other suitable metadata.

In various embodiments, in response to the system determining that the priority of a particular DSAR should be elevated, the system may automatically adjust the deadline for responding to the DSAR. For example, the system may update the deadline in the system's memory and/or modify the “Days Left to Respond” field (See FIG. 13 ) to include a fewer number of days left to respond to the request. Alternatively, or in addition, the system may use other techniques to convey to a respondent that the request should be expedited (e.g., change the color of the request, send a message to the respondent that they should process the request before non-prioritized requests, etc.)

In various embodiments, in response to the system determining that the priority of a particular DSAR should be lowered, the system may automatically adjust the deadline for responding to the DSAR by adding to the number of days left to respond to the request.

Automatic Deletion of Data Subject Records Based on Detected Systems

In particular embodiments, in response a data subject submitting a request to delete their personal data from an organization's systems, the system may: (1) automatically determine where the data subject's personal data is stored; and (2) in response to determining the location of the data (which may be on multiple computing systems), automatically facilitate the deletion of the data subject's personal data from the various systems (e.g., by automatically assigning a plurality of tasks to delete data across multiple business systems to effectively delete the data subject's personal data from the systems). In particular embodiments, the step of facilitating the deletion may comprise, for example: (1) overwriting the data in memory; (2) marking the data for overwrite; (2) marking the data as free (e.g., and deleting a directory entry associated with the data); and/or (3) any other suitable technique for deleting the personal data. In particular embodiments, as part of this process, the system uses an appropriate data model (see discussion above) to efficiently determine where all of the data subject's personal data is stored.

Automatic Determination of Business Processes that Increase Chance of Deletion Requests

In various embodiments, the system is adapted to store, in memory, a log of DSAR actions. The system may also store, in memory, additional information regarding the data subjects of each of the requests. The system may use this information, for example, to determine which business processes are most commonly associated with a data subject submitting a request to have their personal information deleted from the organization's systems. The organization may then use this information to revise the identified business processes in an effort to reduce the number of deletion requests issued by data subjects associated with the business processes.

As a particular example, the system may analyze stored information to determine that a high number (e.g., 15%) of all participants in a company's loyalty program submit requests to have their personal information deleted from the company's systems. In response to making this determination, the system may issue an electronic alert to an appropriate individual (e.g., a privacy officer of the company), informing them of the high rate of members of the company's loyalty program issuing personal data delete requests. This alert may prompt the individual to research the issue and try to resolve it.

Automated Data Subject Verification

In various embodiments, before a data subject request can be processed, the data subject's identity may need to be verified. In various embodiments, the system provides a mechanism to automatically detect the type of authentication required for a particular data subject based on the type of Data Subject Access Request being made and automatically issues a request to the data subject to verify their identity against that form of identification. For example, a subject rights request might only require two types of authentication, but a deletion request may require four types of data to verify authentication. The system may automatically detect which is type of authentication is required based on the DSAR and send an appropriate request to the data subject to verify their identity.

Stated more particularly, when processing a data subject access request, the system may be configured to verify an identity of the data subject prior to processing the request (e.g., or as part of the processing step). In various embodiments, confirming the identity of the data subject may, for example, limit a risk that a third-party or other entity may gain unlawful or unconsented to access to the requestor's personal data. The system may, for example, limit processing and fulfillment of requests relating to a particular data subject to requests that are originated by (e.g., received from) the particular data subject. When processing a data subject access request, the system may be configured to use various reasonable measures to verify the identity of the data subject who requests access (e.g., in particular in the context of online services and online identifiers). In particular embodiments, the system is configured to substantially automatically validate an identity of a data subject when processing the data subject access request.

For example, in particular embodiments, the system may be configured to substantially automatically (e.g., automatically) authenticate and/or validate an identity of a data subject using any suitable technique. These techniques may include, for example: (1) one or more credit-based and/or public- or private-information-based verification techniques; (2) one or more company verification techniques (e.g., in the case of a business-to-business data subject access request); (3) one or more techniques involving integration with a company's employee authentication system; (4) one or more techniques involving a company's (e.g., organization's) consumer portal authentication process; (5) etc. Various exemplary techniques for authenticating a data subject are discussed more fully below.

In particular embodiments, when authenticating a data subject (e.g., validating the data subject's identity), the system may be configured to execute particular identity confirmation steps, for example, by interfacing with one or more external systems (e.g., one or more third-party data aggregation systems). For example, the system, when validating a data subject's identity, may begin by verifying that a person with the data subject's name, address, social security number, or other identifying characteristic (e.g., which may have been provided by the data subject as part of the data subject access request) actually exists. In various embodiments, the system is configured to interface with (e.g., transmit a search request to) one or more credit reporting agencies (e.g., Experian, Equifax, TransUnion, etc.) to confirm that a person with one or more characteristics provided by the data subject exists. The system may, for example, interface with such credit reporting agencies via a suitable plugin (e.g., software plugin). Additionally, there might be a verification on behalf of a trusted third-party system (e.g., the controller).

In still other embodiments, the system may be configured to utilize one or more other third-party systems (e.g., such as LexisNexis, IDology, RSA, etc.), which may, for example, compile utility and phone bill data, property deeds, rental agreement data, and other public records for various individuals. The system may be configured to interface with one or more such third-party systems to confirm that a person with one or more characteristics provided by the data subject exists.

After the step of confirming the existence of a person with the one or more characteristics provided by the data subject, the system may be configured to confirm that the person making the data subject access request is, in fact, the data subject. The system may, for example, verify that the requestor is the data subject by prompting the requestor to answer one or more knowledge-based authentication questions (e.g., out-of-wallet questions). In particular embodiments, the system is configured to utilize one or more third-party services as a source of such questions (e.g., any of the suitable third-party sources discussed immediately above). The system may use third-party data from the one or more third-party sources to generate one or more questions. These one or more questions may include questions that a data subject should know an answer to without knowing the question ahead of time (e.g., one or more previous addresses, a parent or spouse name and/or maiden name, etc.).

FIG. 46 depicts an exemplary identity verification questionnaire. As may be understood from this figure, an identity verification questionnaire may include one or more questions whose responses include data that the system may derive from one or more credit agencies or other third-party data aggregation services (e.g., such as previous street addresses, close associates, previous cities lived in, etc.). In particular embodiments, the system is configured to provide these one or more questions to the data subject in response to receiving the data subject access request. In other embodiments, the system is configured to prompt the data subject to provide responses to the one or more questions at a later time (e.g., during processing of the request). In particular other embodiments, the system is configured to substantially automatically compare one or more pieces of information provided as part of the data subject access request to one or more pieces of data received from a third-party data aggregation service in order to substantially automatically verify the requestor's identity.

In still other embodiments, the system may be configured to prompt a requestor to provide one or more additional pieces of information in order to validate the requestor's identity. This information may include, for example: (1) at least a portion of the requestor's social security number (e.g., last four digits); (2) a name and/or place of birth of the requestor's father; (3) a name, maiden name, and/or place of birth of the requestor's mother; and/or (4) any other information which may be useful for confirming the requestor's identity (e.g., such as information available on the requestor's birth certificate). In other embodiments, the system may be configured to prompt the requestor to provide authorization for the company to check the requestor's social security or other private records (e.g., credit check authorization, etc.) to obtain information that the system may use to confirm the requestor's identity. In other embodiments, the system may prompt the user to provide one or more images (e.g., using a suitable mobile computing device) of an identifying document (e.g., a birth certificate, social security card, driver's license, etc.).

The system may, in response to a user providing one or more responses that matches information that the system receives from one or more third-party data aggregators or through any other suitable background, credit, or other search, substantially automatically authenticate the requestor as the data subject. The system may then continue processing the data subject's request, and ultimately fulfill their request.

In particular embodiments, such as embodiments in which the requestor includes a business (e.g., as in a business to business data subject access request), the system may be configured to authenticate the requesting business using one or more company verification techniques. These one or more company validation techniques may include, for example, validating a vendor contract (e.g., between the requesting business and the company receiving the data subject access request); receiving a matching token, code, or other unique identifier provided by the company receiving the data subject access request to the requesting business; receiving a matching file in possession of both the requesting business and the company receiving the data subject access request; receiving a signed contract, certificate (e.g., digital or physical), or other document memorializing an association between the requesting business and the company receiving the data subject access request; and/or any other suitable method of validating that a particular request is actually made on behalf of the requesting business (e.g., by requesting the requesting business to provide one or more pieces of information, one or more files, one or more documents, etc. that may only be accessible to the requesting business).

In other embodiments, the system may be configured to authenticate a request via integration with a company's employee or customer (e.g., consumer) authentication process. For example, in response to receiving a data subject access request that indicates that the data subject is an employee of the company receiving the data subject access request, the system may be configured to prompt the employee to login to the company's employee authentication system (e.g., Okta, Azure, AD, etc.) In this way, the system may be configured to authenticate the requestor based at least in part on the requestor successfully logging into the authentication system using the data subject's credentials. Similarly, in response to receiving a data subject access request that indicates that the data subject is a customer of the company receiving the data subject access request, the system may be configured to prompt the customer to login to an account associated with the company (e.g., via a consumer portal authentication process). In a particular example, this may include, for example, an Apple ID (for data subject access requests received by Apple). In this way, the system may be configured to authenticate the requestor based at least in part on the requestor successfully logging into the authentication system using the data subject's credentials. In some embodiments, the system may be configured to require the requestor to login using two-factor authentication or other suitable existing employee or consumer authentication process.

Data Subject Blacklist

In various embodiments, a particular organization may not be required to respond to a data subject access request that originates (e.g., is received from) a malicious requestor. A malicious requestor may include, for example: (1) a requestor (e.g., an individual) that submits excessive or redundant data subject access requests; (2) a group of requestors such as researchers, professors, students, NGOs, etc. that submit a plurality of requests for reasons other than those reasons provided by policy, law, etc.; (3) a competitor of the company receiving the data subject access request that is submitting such requests to tie up the company's resources unnecessarily; (4) a terrorist or other organization that may spam requests to disrupt the company's operation and response to valid requests; and/or (5) any other request that may fall outside the scope of valid requests made for reasons proscribed by public policy, company policy, or law. In particular embodiments, the system is configured to maintain a blacklist of such malicious requestors.

In particular embodiments, the system is configured to track a source of each data subject access request and analyze each source to identify sources from which: (1) the company receives a large volume of requests; (2) the company receives a large number of repeat requests; (3) etc. These sources may include, for example: (1) one or more particular IP addresses; (2) one or more particular domains; (3) one or more particular countries; (4) one or more particular institutions; (5) one or more particular geographic regions; (6) etc. In various embodiments, in response to analyzing the sources of the requests, the system may identify one or more sources that may be malicious (e.g., are submitting excessive requests).

In various embodiments, the system is configured to maintain a database of the identified one or more sources (e.g., in computer memory). In particular embodiments, the database may store a listing of identities, data sources, etc. that have been blacklisted (e.g., by the system). In particular embodiments, the system is configured to, in response to receiving a new data subject access request, cross reference the request with the blacklist to determine if the requestor is on the blacklist or is making the request from a blacklisted source. The system may then, in response to determining that the requestor or source is blacklisted, substantially automatically reject the request. In particular embodiments, the blacklist cross-referencing step may be part of the requestor authentication (e.g., verification) discussed above. In various embodiments, the system may be configured to analyze request data on a company by company basis to generate a blacklist. In other embodiments, the system may analyze global data (e.g., all data collected for a plurality of companies that utilize the data subject access request fulfillment system) to generate the blacklist.

In particular embodiments, the system may be configured to fulfill data subject access requests for the purpose of providing a data subject with information regarding what data the company collects and for what purpose, for example, so the data subject can ensure that the company is collecting data for lawful reasons. As such, the system may be configured to identify requestors and other sources of data requests that are made for other reasons (e.g., one or more reasons that would not obligate the company to respond to the request). These reasons may include, for example, malicious or other reasons such as: (1) research by an academic institution by one or more students or professors; (2) anticompetitive requests by one or more competitors; (3) requests by disgruntled former employees for nefarious reasons; (4) etc.

In particular embodiments, the system may, for example, maintain a database (e.g., in computer memory) of former employees. In other embodiments, the system may, for example: (1) identify a plurality of IP addresses associated with a particular entity (e.g., academic organization, competitor, etc.); and (2) substantially automatically reject a data subject access request that originates from the plurality of IP addresses. In such embodiments, the system may be configured to automatically add such identified IP addresses and/or domains to the blacklist.

In still other embodiments, the system is configured to maintain a listing of blacklisted names of particular individuals. These may include, for example, one or more individuals identified (e.g., by an organization or other entity) as submitting malicious data subject access requests).

FIG. 47 depicts a queue of pending data subject access requests. As shown in this figure, the first three listed data subject access requests are new and require verification before processing and fulfillment can begin. As shown in this figure, a user (e.g., such as a privacy officer or other privacy controller) may select a particular request, and select an indicia for verifying the request. The user may also optionally select to reject the request. FIG. 48 depicts an authentication window that enables the user to authenticate a particular request. In various embodiments, the user may provide an explanation of why the user is authenticating the request (e.g., because the requestor successfully completed on or more out-of-wallet questions or for any other suitable reason). The user may further submit one or more attachments to support the verification. In this way, the system may be configured to document that the authentication process was performed for each request (e.g., in case there was an issue with improperly fulfilling a request, the company could show that they are following procedures to prevent such improper processing). In other embodiments, the system may enable the user to provide similar support when rejecting a request (e.g., because the requestor was blacklisted, made excessive requests, etc.).

Data Subject Access Request Fulfillment Cost Determination

In various embodiments, as may be understood in light of this disclosure, fulfilling a data subject access request may be particularly costly. In some embodiments, a company may store data regarding a particular data subject in multiple different locations for a plurality of different reasons as part of a plurality of different processing and other business activities. For example, a particular data subject may be both a customer and an employee of a particular company or organization. Accordingly, in some embodiments, fulfilling a data subject access request for a particular data subject may involve a plurality of different information technology (IT) professionals in a plurality of different departments of a particular company or organization. As such, it may be useful to determine a cost of a particular data subject access request (e.g., particularly because, in some cases, a data subject is entitled to a response to their data subject access request as a matter of right at no charge).

In particular embodiments, in response to receiving a data subject access request, the system may be configured to: (1) assign the request to at least one privacy team member; (2) identify one or more IT teams required to fulfill the request (e.g., one or more IT teams associated with one or more business units that may store personal data related to the request); (3) delegate one or more subtasks of the request to each of the one or more IT teams; (4) receive one or more time logs from each individual involved in the processing and fulfillment of the data subject access request; (5) calculate an effective rate of each individual's time (e.g., based at least in part on the individual's salary, bonus, benefits, chair cost, etc.); (6) calculate an effective cost of fulfilling the data subject access request based at least in part on the one or more time logs and effective rate of each of the individual's time; and (7) apply an adjustment to the calculated effective cost that accounts for one or more external factors (e.g., overhead, etc.) in order to calculate a cost of fulfilling the data subject access request.

In particular embodiments, the system is configured to substantially automatically track an amount of time spent by each individual involved in the processing and fulfillment of the data subject access request. The system may, for example, automatically track an amount of time between each individual opening and closing a ticket assigned to them as part of their role in processing or fulfilling the data subject access request. In other embodiments, the system may determine the time spent based on an amount of time provided by each respective individual (e.g., the individual may track their own time and submit it to the system).

In various embodiments, the system is configured to measure a cost of each particular data subject access request received, and analyze one or more trends in costs of, for example: (1) data subject access requests over time; (2) related data subject access requests; (3) etc. For example, the system may be configured to track and analyze cost and time-to-process trends for one or more social groups, one or more political groups, one or more class action groups, etc. In particular, the system may be configured to identify a particular group from which the system receives particularly costly data subject access request (e.g., former and/or current employees, members of a particular social group, members of a particular political group, etc.).

In particular embodiments, the system may be configured to utilize data subject access request cost data when processing, assigning, and/or fulfilling future data subject access requests (e.g., from a particular identified group, individual, etc.). For example, the system may be configured to prioritize requests that are expected to be less costly and time-consuming (e.g., based on past cost data) over requests identified as being likely more expensive. Alternatively, the system may prioritize more costly and time-consuming requests over less costly ones in the interest of ensuring that the system is able to respond to each request in a reasonable amount of time (e.g., within a time required by law, such as a thirty day period, or any other suitable time period).

Customer Satisfaction Integration with Data Subject Access Requests

In various embodiments, the system may be configured to collect customer satisfaction data, for example: (1) as part of a data subject access request submission form; (2) when providing one or more results of a data subject access request to the data subject; or (3) at any other suitable time. In various embodiments, the customer satisfaction data may be collected in the form of a suitable survey, free-form response questionnaire, or other suitable satisfaction data collection format (e.g., thumbs up vs. thumbs down, etc.).

FIG. 49 depicts an exemplary customer satisfaction survey that may be included as part of a data subject access request form, provided along with the results of a data subject access request, provided in one or more messages confirming receipt of a data subject access request, etc. As shown in the figure, the customer satisfaction survey may relate to how likely a customer (e.g., a data subject) is to recommend the company (e.g., to which the data subject has submitted the request) to a friend (e.g., or colleague). In the example shown in FIG. 49 , the satisfaction survey may relate to a Net Promoter score (NPS), which may indicate a loyalty of a company's customer relationships. Generally speaking, the Net Promoter Score may measure a loyalty that exists between a provider and a consumer. In various embodiments, the provider may include a company, employer, or any other entity. In particular embodiments, the consumer may include a customer, employee, or other respondent to an NPS survey.

In particular embodiments, the question depicted in FIG. 49 is the primary question utilized in calculating a Net Promoter Score (e.g., “how likely is it that you would recommend our company/product/service to a friend or colleague?”). In particular embodiments, the question is presented with responses ranging from 0 (not at all likely) to 10 (extremely likely). In particular embodiments, the question may include any other suitable scale. As may be understood from FIG. 49 , the system may be configured to assign particular categories to particular ratings on the 10 point scale. The system may be configured to track and store responses provided by consumers and calculate an overall NPS score for the provider. The system may be further configured to generate a visual representation of the NPS score, including a total number of responses received for each particular score and category as shown in FIG. 49 .

In various embodiments, the system may be configured to measure data related to any other suitable customer satisfaction method (e.g., in addition to NPS). By integrating a customer satisfaction survey with the data subject access request process, the system may increase a number of consumers that provide one or more responses to the customer satisfaction survey. In particular embodiments, the system is configured to require the requestor to respond to the customer satisfaction survey prior to submitting the data subject access request.

Identifying and Deleting Orphaned Data

In particular embodiments, an Orphaned Data Action System is configured to analyze one or more data systems (e.g., data assets), identify one or more pieces of personal data that are one or more pieces of personal data that are not associated with one or more privacy campaigns of the particular organization, and notify one or more individuals of the particular organization of the one or more pieces of personal data that are one or more pieces of personal data that are not associated with one or more privacy campaigns of the particular organization. In various embodiments, one or more processes described herein with respect to the orphaned data action system may be performed by any suitable server, computer, and/or combination of servers and computers.

Various processes performed by the Orphaned Data Action System may be implemented by an Orphaned Data Action Module 5000. Referring to FIG. 50 , in particular embodiments, the system, when executing the Orphaned Data Action Module 5000, is configured to: (1) access one or more data assets of a particular organization; (2) scan the one or more data assets to generate a catalog of one or more privacy campaigns and one or more pieces of personal information associated with one or more individuals; (3) store the generated catalog in computer memory; (4) scan one or more data assets based at least in part on the generated catalog to identify a first portion of the one or more pieces of personal data that are one or more pieces of personal data that are not associated with the one or more privacy campaigns; (5) generate an indication that the first portion of one or more pieces of personal data that are not associated with the one or more privacy campaigns of the particular organization is to be removed from the one or more data assets; (6) present the indication to one or more individuals associated with the particular organization; and (7) remove the first portion of the one or more pieces of personal data that are not associated with the one or more privacy campaigns of the particular organization from the one or more data assets.

When executing the Orphaned Data Action Module 5000, the system begins, at Step 5010, by accessing one or more data systems associated with the particular entity. The particular entity may include, for example, a particular organization, company, sub-organization, etc. In particular embodiments, the one or more data assets (e.g., data systems) may include, for example, any entity that collects, processes, contains, and/or transfers data (e.g., a software application, “internet of things” computerized device, database, website, data-center, server, etc.). For example, a data asset may include any software or device utilized by a particular entity for data collection, processing, transfer, storage, etc.

In particular embodiments, the system is configured to identify and access the one or more data assets using one or more data modeling techniques. As discussed more fully above, a data model may store the following information: (1) the entity that owns and/or uses a particular data asset; (2) one or more departments within the organization that are responsible for the data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the data asset; (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to for other use, and which particular data is transferred to each of those data assets.

As may be understood in light of this disclosure, the system may utilize a data model (e.g., or one or more data models) of data assets associated with a particular entity to identify and access the one or more data assets associated with the particular entity.

Continuing to Step 5020, the system is configured to scan the one or more data assets to generate a catalog of one or more privacy campaigns and one or more pieces of personal information associated with one or more individuals. The catalog may include a table of the one or more privacy campaigns within the data assets of the particular entity and, for each privacy campaign, the one or more pieces of personal data stored within the data assets of the particular entity that are associated with the particular privacy campaign. In any embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein.

In some implementations, the system may access, via one or more computer networks, one or more data models that map an association between one or more pieces of personal data stored within one or more data assets of the particular entity and one or more privacy campaigns of the particular entity. As further described herein, the data models may access the data assets of the particular entity and use one or more suitable data mapping techniques to link, or otherwise associate, the one or more pieces of personal data stored within one or more data assets of the particular entity and one or more privacy campaigns of the particular entity. In some implementations, the one or more data models may link, or otherwise associate, a particular individual and each piece of personal data of that particular individual that is stored on one or more data assets of the particular entity.

In some embodiments, the system is configured to generate and populate a data model based at least in part on existing information stored by the system (e.g., in one or more data assets), for example, using one or more suitable scanning techniques. In still other embodiments, the system is configured to access an existing data model that maps personal data stored by one or more organization systems to particular associated processing activities. In some implementations, the system is configured to generate and populate a data model substantially on the fly (e.g., as the system receives new data associated with particular processing activities). For example, a particular processing activity (e.g., privacy campaign) may include transmission of a periodic advertising e-mail for a particular company (e.g., a hardware store). A data model may locate the collected and stored email addresses for customers that elected to receive (e.g., consented to receipt of) the promotional email within the data assets of the particular entity, and then map each of the stored email addresses to the particular processing activity (i.e., the transmission of a periodic advertising e-mail) within the data assets of the particular entity.

Next, at Step 5030, the system is configured to store the generated catalog of one or more privacy campaigns and one or more pieces of personal information associated with one or more individuals. In some implementations, the system may receive an indication that a new processing activity (e.g., privacy campaign) has been launched by the particular entity. In response to receiving the indication, the system may modify the one or more data models to map an association between (i) one or more pieces of personal data associated with one or more individuals obtained in connection with the new privacy campaign and (ii) the new privacy campaign initiated by the particular entity. As the system receives one or more pieces of personal data associated with one or more individuals (e.g., an email address signing up to receive information from the particular entity), then the data model associated with the particular processing activity may associate the received personal data with the privacy campaign. In some implementations, one or more data assets may already include the particular personal data (e.g., email address) because the particular individual, for example, previously provided their email address in relation to a different privacy campaign of the particular entity. In response, the system may access the particular personal data and associate that particular personal data with the new privacy campaign.

At Step 5040, the system is configured to scan one or more data assets based at least in part on the generated catalog to identify a first portion of the one or more pieces of personal data that are one or more pieces of personal data that are not associated with the one or more privacy campaigns. In various embodiments, the system may use the generated catalogue to scan the data assets of the particular entity to identify personal data that has been collected and stored using one or more computer systems operated and/or utilized by a particular organization where the personal data is not currently being used as part of any privacy campaigns, processing activities, etc. undertaken by the particular organization. The one or more pieces of personal data that are not associated with the one or more privacy campaigns may be a portion of the personal data that is stored by the particular entity. In some implementations, the system may analyze the data models to identify the one or more pieces of personal data that are not associated with the one or more privacy campaigns.

When the particular privacy campaign, processing activity, etc. is terminated or otherwise discontinued, the system may determine if any of the associated personal data that has been collected and stored by the particular organization is now orphaned data. In some implementations, in response to the termination of a particular privacy campaign and/or processing activity, (e.g., manually or automatically), the system may be configured to scan one or more data assets based at least in part on the generated catalog or analyze the data models to determine whether any of the personal data that has been collected and stored by the particular organization is now orphaned data (e.g., whether any personal data collected and stored as part of the now-terminated privacy campaign is being utilized by any other processing activity, has some other legal basis for its continued storage, etc.). In some implementations, the system may generate an indication that one or more pieces of personal data that are associated with the terminated one or more privacy campaigns are included in the portion of the one or more pieces of personal data (e.g., orphaned data).

In additional implementations, the system may determine that a particular privacy campaign, processing activity, etc. has not been utilized for a period of time (e.g., a day, a month, a year). In response, the system may be configured to terminate the particular processing activity, processing activity, etc. In some implementations, in response to the system determining that a particular processing activity has not been utilized for a period of time, the system may prompt one or more individuals associated with the particular entity to indicate whether the particular privacy campaign should be terminated or otherwise discontinued.

For example, a particular processing activity may include transmission of a periodic advertising e-mail for a particular company (e.g., a hardware store). As part of the processing activity, the particular company may have collected and stored e-mail addresses for customers that elected to receive (e.g., consented to the receipt of) the promotional e-mails. In response to determining that the particular company has not sent out any promotional e-mails for at least a particular amount of time (e.g., for at least a particular number of months), the system may be configured to: (1) automatically terminate the processing activity; (2) identify any of the personal data collected as part of the processing activity that is now orphaned data (e.g., the e-mail addresses); and (3) automatically delete the identified orphaned data. The processing activity may have ended for any suitable reason (e.g., because the promotion that drove the periodic e-mails has ended). As may be understood in light of this disclosure, because the particular organization no longer has a valid basis for continuing to store the e-mail addresses of the customers once the e-mail addresses are no longer being used to send promotional e-mails, the organization may wish to substantially automate the removal of personal data stored in its computer systems that may place the organization in violation of one or more personal data storage rules or regulations.

Continuing to Step 5050, the system is configured to generate an indication that the portion of one or more pieces of personal data that are not associated with the one or more privacy campaigns of the particular entity is to be removed from the one or more data assets. At Step 5060, the system is configured to present the indication to one or more individuals associated with the particular entity. The indication may be an electronic notification to be provided to an individual (e.g., privacy officer) associated with the particular entity. The electronic notification may be, for example, (1) a notification within a software application (e.g., a data management system for the one or more data assets of the particular entity), (2) an email notification, (3) etc.

In some implementations, the indication may enable the individual (e.g., privacy officer of the particular entity) to select a set of the one or more pieces of personal data of the portion of the one or more pieces of personal data to retain based on one or more bases to retain the set of the one or more pieces of personal data.

In particular embodiments, the system may prompt the one or more individuals to provide one or more bases to retain the first set of the one or more pieces of personal data of the first portion of the one or more pieces of personal data that are not associated with the one or more privacy campaigns. In some implementations, in response to receiving the provided one or more valid bases to retain the first set of the one or more pieces of personal data from the one or more individuals associated with the particular entity, submitting the provided one or more valid bases to retain the first set of the one or more pieces of personal data to one or more second individuals associated with the particular entity for authorization. In response, the system may retain the first set of the one or more pieces of personal data of the first portion of the one or more pieces of personal data from the one or more individuals associated with the particular entity. Further, the system may remove a second set of the one or more pieces of personal data of the first portion of the one or more pieces of personal data that are not associated with the one or more privacy campaigns from the one or more data assets. In particular embodiments, the second set of the one or more pieces of personal data may be different from the first set of the one or more pieces of personal data.

Continuing to Step 5070, the system is configured to remove, by one or more processors, the first portion of the one or more pieces of personal data that are not associated with the one or more privacy campaigns of the particular entity from the one or more data assets.

Data Testing to Confirm Deletion Under a Right to Erasure

In particular embodiments, a Personal Data Deletion System is configured to: (1) at least partially automatically identify and delete personal data that an entity is required to erase under one or more of the conditions discussed above; and (2) perform one or more data tests after the deletion to confirm that the system has, in fact, deleted any personal data associated with the data subject.

Various processes performed by the Personal Data Deletion System may be implemented by a Personal Data Deletion and Testing Module 5100. Referring to FIG. 51 , in particular embodiments, the system, when executing the Personal Data Deletion and Testing Module 5100, is configured to: (1) receive an indication that the entity has completed an erasure of one or more pieces of personal data associated with the data subject under a right of erasure; (2) initiate a test interaction between the data subject and the entity, the test interaction requiring a response from the entity to the data subject; (3) determine whether one or more system associated with the entity have initiated a test interaction response to the data subject based at least in part on the test interaction; (4) in response to determining that the one or more systems associated with the entity have initiated the test interaction response, (a) determine that the entity has not completed the erasure of the one or more pieces of personal data associated with the data subject and (b) automatically take one or more actions with regard to the personal data associated with the data subject.

When executing the Personal Data Deletion and Testing Module 5100, the system begins, at Step 5110, by receiving an indication that the entity has completed an erasure of one or more pieces of personal data associated with the data subject under a right of erasure. The particular entity may include, for example, a particular organization, company, sub-organization, etc. In particular embodiments, the one or more computers systems may be configured to store (e.g., in memory) an indication that the data subject's request to delete any of their personal data stored by the one or more computers systems has been processed. Under various legal and industry policies/standards, the organization may have a certain period of time (e.g., a number of days) in order to comply with the one or more requirements related to the deletion or removal of personal data in response to receiving a request from the data subject or in response to identifying one or more of the conditions requiring deletion discussed above. In response to the receiving an indication that the deletion request for the data subject's personal data has been processed or the certain period of time (described above) has passed, the system may be configured to perform a data test to confirm the deletion of the data subject's personal data.

Continuing to Step 5120, in response to receiving the indication that the entity has completed the erasure, the system is configured to initiate a test interaction between the data subject and the entity, the test interaction requiring a response from the entity to the data subject. In particular embodiments, when performing the data test, the system may be configured to provide an interaction request to the entity on behalf of the data subject. In particular embodiments, the interaction request may include, for example, a request for one or more pieces of data associated with the data subject (e.g., account information, etc.). In various embodiments, the interaction request is a request to contact the data subject (e.g., for any suitable reason). The system may, for example, be configured to substantially automatically complete a contact-request form (e.g., a webform made available by the entity) on behalf of the data subject. In various embodiments, when automatically completing the form on behalf of the data subject, the system may be configured to only provide identifying data, but not to provide any contact data. In response to submitting the interaction request (e.g., submitting the webform), the system may be configured to determine whether the one or more computers systems have generated and/or transmitted a response to the data subject. The system may be configured to determine whether the one or more computers systems have generated and/or transmitted the response to the data subject by, for example, analyzing one or more computer systems associated with the entity to determine whether the one or more computer systems have generated a communication to the data subject (e.g., automatically) for transmission to an e-mail address or other contact method associated with the data subject, generated an action-item for an individual to contact the data subject at a particular contact number, etc.

To perform the data test, for example, the system may be configured to: (1) access (e.g., manually or automatically) a form for the entity (e.g., a web-based “Contact Us” form); (2) input a unique identifier associated with the data subject (e.g., a full name or customer ID number) without providing contact information for the data subject (e.g., mailing address, phone number, email address, etc.); and (3) input a request, within the form, for the entity to contact the data subject to provide information associated with the data subject (e.g., the data subject's account balance with the entity). In response to submitting the form to the entity, the system may be configured to determine whether the data subject is contacted (e.g., via a phone call or email) by the one or more computers systems (e.g., automatically). In some implementations, completing the contact-request form may include providing one or more pieces of identifying data associated with the data subject, the one or more pieces of identifying data comprising data other than contact data. In response to determining that the data subject has been contacted following submission of the form, the system may determine that the one or more computers systems have not fully deleted the data subject's personal data (e.g., because the one or more computers systems must still be storing contact information for the data subject in at least one location).

In particular embodiments, the system is configured to generate one or more test profiles for one or more test data subjects. For each of the one or more test data subjects, the system may be configured to generate and store test profile data such as, for example: (1) name; (2) address; (3) telephone number; (4) e-mail address; (5) social security number; (6) information associated with one or more credit accounts (e.g., credit card numbers); (7) banking information; (8) location data; (9) internet search history; (10) non-credit account data; and/or (11) any other suitable test data. The system may then be configured to at least initially consent to processing or collection of personal data for the one or more test data subjects by the entity. The system may then request deletion of data of any personal data associated with a particular test data subject. In response to requesting the deletion of data for the particular test data subject, the system may then take one or more actions using the test profile data associated with the particular test data subjects in order to confirm that the one or more computers systems have, in fact, deleted the test data subject's personal data (e.g., any suitable action described herein). The system may, for example, be configured to: (1) initiate a contact request on behalf of the test data subject; (2) attempt to login to one or more user accounts that the system had created for the particular test data subject; and/or (3) take any other action, the effect of which could indicate a lack of complete deletion of the test data subject's personal data.

Next, at Step 5130, in response to initiating the test interaction, the system is configured to determine whether one or more system associated with the entity have initiated a test interaction response to the data subject based at least in part on the test interaction. In response to determining that the entity has generated a response to the test interaction, the system may be configured to determine that the entity has not complied with the data subject's request (e.g., deletion of their personal data from the one or more computers systems). For example, if the test interaction requests for the entity to locate and provide any personal data the system has stored related to the data subject, then by the system providing a response that includes one or more pieces of personal data related to the data subject, the system may determine that the one or more computers systems have not complied with the request. As described above, the request may be an erasure of one or more pieces of personal data associated with the data subject under a right of erasure. In some implementations, the test interaction response may be any response that includes any one of the one or more pieces of personal data the system indicated was erased under the right of erasure. In some implementations, the test interaction response may not include response that indicates that the one or more pieces of personal data the system indicated was erased under the right of erasure was not found or accessed by the system.

At Step 5140, in response to determining that the one or more systems associated with the entity have initiated the test interaction response the system is configured to (a) determine that the one or more computers systems have not completed the erasure of the one or more pieces of personal data associated with the data subject, and (b) automatically take one or more actions with regard to the personal data associated with the data subject. In response to determining that the one or more computers systems have not fully deleted a data subject's (e.g., or test data subject's) personal data, the system may then be configured, in particular embodiments, to: (1) flag the data subject's personal data for follow up by one or more privacy officers to investigate the lack of deletion; (2) perform one or more scans of one or more computing systems associated with the entity to identify any residual personal data that may be associated with the data subject; (3) generate a report indicating the lack of complete deletion; and/or (4) take any other suitable action to flag the data subject, personal data, initial request to be forgotten, etc. for follow up.

In various embodiments, the one or more actions may include: (1) identifying the one or more pieces of personal data associated with the data subject that remain stored in the one or more computer systems of the entity; (2) flagging the one or more pieces of personal data associated with the data subject that remain stored in the one or more computer systems of the entity; and (3) providing the flagged one or more pieces of personal data associated with the data subject that remain stored in the one or more computer systems of the entity to an individual associated with the entity.

In various embodiments, the system may monitor compliance by a particular entity with a data subject's request to delete the data subject's personal data from the one or more computers systems associated with a particular entity. The system may, for example, be configured to test to ensure the data has been deleted by: (1) submitting a unique token of data through a webform to a system (e.g., mark to); (2) in response to passage of an expected data retention time, test the system by calling into the system after the passage of the data retention time to search for the unique token. In response to finding the unique token, the system may be configured to determine that the data has not been properly deleted.

The system may provide a communication to the entity that includes a unique identifier associated with the data subject, is performed without using a personal communication data platform, prompts the entity to provide a response by contacting the data subject via a personal communication data platform. In response to providing the communication to the entity, the system may determine whether the data subject has received a response via the personal communication data platform. The system may, in response to determining that the data subject has received the response via the personal communication data platform, determine that the one or more computers systems have not complied with the data subject's request for deletion of their personal data. In response, the system may generate an indication that the one or more computers systems have not complied with the data subject's request for deletion of their personal data by the entity, and digitally store the indication that the one or more computers systems have not complied with the data subject's request for deletion of their personal data in computer memory.

Automatic Preparation for Remediation

In particular embodiments, a Risk Remediation System is configured to substantially automatically determine whether to take one or more actions in response to one or more identified risk triggers. For example, an identified risk trigger may be that a data asset for an organization is hosted in only one particular location thereby increasing the scope of risk if the location were infiltrated (e.g., via cybercrime). In particular embodiments, the system is configured to substantially automatically perform one or more steps related to the analysis of and response to the one or more potential risk triggers discussed above. For example, the system may substantially automatically determine a relevance of a risk posed by (e.g., a risk level) the one or more potential risk triggers based at least in part on one or more previously-determined responses to similar risk triggers. This may include, for example, one or more previously determined responses for the particular entity that has identified the current risk trigger, one or more similarly situated entities, or any other suitable entity or potential trigger.

Various processes performed by the Risk Remediation System may be implemented by a Data Risk Remediation Module 5200. Referring to FIG. 52 , in particular embodiments, the system, when executing the Data Risk Remediation Module 5200, is configured to access risk remediation data for an entity that identifies one or more actions to remediate a risk in response to identifying one or more data assets of the entity potentially affected by one or more risk triggers, receive an indication of an update to the one or more data assets, identify one or more updated risk triggers for an entity based at least in part on the update to the one or more data assets, determine, by using one or more data models associated with the risk remediation data, one or more updated actions to remediate the one or more updated risk triggers, analyze the one or more updated risk triggers to determine a relevance of the risk posed to the entity by the one or more updated risk triggers, and update the risk remediation data to include the one or more updated actions to remediate the risk in response to identifying the one or more updated risk triggers.

When executing the Data Risk Remediation Module 5200, the system begins, at Step 5210, by accessing risk remediation data for an entity that identifies one or more actions to remediate a risk in response to identifying one or more data assets of the entity potentially affected by one or more risk triggers. The particular entity may include, for example, a particular organization, company, sub-organization, etc. The one or more data assets may include personal data for clients or customers. In embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein.

In some implementations, the system may include risk remediation data associated with one or more data assets. The risk remediation data may be default or pre-configured risk remediation data that identifies one or more actions to remediate a risk in response to identifying one or more data assets of the entity potentially affected by one or more risk triggers. In some implementations, the system may have previously updated and/or continuously update the risk remediation data. The risk remediation data may be updated and/or based on aggregate risk remediation data for a plurality of identified risk triggers from one or more organizations, which may include the entity.

The system may analyze the aggregate risk remediation data to determine a remediation outcome for each of the plurality of identified risk triggers and an associated entity response to the particular identified risk trigger of the plurality of identified risk triggers. The remediation outcome is an indication of how well the entity response addressed the identified risk trigger. For example, the remediation outcome can be a numerical (e.g., 1 to 10), an indication of the risk trigger after the entity response was performed (e.g., “high,” “medium,” or “low”). In response to analyzing the aggregate risk remediation data to determine a remediation outcome for each of the plurality of identified risk triggers and an associated entity response to the particular identified risk trigger of the plurality of identified risk triggers, generating the data model of the one or more data models.

One or more data models for the system may be generated to indicate a recommended entity response based on each identified risk trigger. The one or more risk remediation models base be generated in response to analyzing the aggregate risk remediation data to determine a remediation outcome for each of the plurality of identified risk triggers and an associated entity response to the particular identified risk trigger of the plurality of identified risk triggers. Additionally, the risk remediation data for the entity may include the one or more risk remediation data models with an associated one or more data assets of the entity.

Continuing to Step 5220, the system is configured to receive an indication of an update to the one or more data assets. In particular embodiments, the system may indicate that a modification has been performed to the one or more data assets. In various embodiments, when a privacy campaign, processing activity, etc. of the particular organization is modified (e.g., add, remove, or update particular information), then the system may the risk remediation data for use in facilitating an automatic assessment of and/or response to future identified risk triggers. The modification may be an addition (e.g., additional data stored to the one or more data assets), a deletion (e.g., removing data stored to the one or more data assets), or a change (e.g., editing particular data or rearranging a configuration of the data associated with the one or more data assets. At Step 5230, the system is configured to identify one or more updated risk triggers for an entity based at least in part on the update to the one or more data assets. The updated risk triggers may be anything that exposes the one or more data assets of the entity to, for example, a data breach or a loss of data, among others. For example, an identified risk trigger may be that a data asset for an organization is hosted in only one particular location thereby increasing the scope of risk if the location were infiltrated (e.g., via cybercrime).

At Step 5240, the system is configured to determine, by using one or more data models associated with the risk remediation data, one or more updated actions to remediate the one or more updated risk triggers. As previously described above, the one or more data models for the system may be generated to indicate a recommended entity response based on each identified risk trigger. The one or more risk remediation models base be generated in response to analyzing the aggregate risk remediation data to determine a remediation outcome for each of the plurality of identified risk triggers and an associated entity response to the particular identified risk trigger of the plurality of identified risk triggers.

At Step 5250, the system is configured to analyze the one or more updated risk triggers to determine a relevance of the risk posed to the entity by the one or more updated risk triggers. In particular embodiments, the system is configured to substantially automatically perform one or more steps related to the analysis of and response to the one or more potential risk triggers discussed above. For example, the system may substantially automatically determine a relevance of a risk posed by (e.g., a risk level) the one or more potential risk triggers based at least in part on one or more previously-determined responses to similar risk triggers. This may include, for example, one or more previously determined responses for the particular entity that has identified the current risk trigger, one or more similarly situated entities, or any other suitable entity or potential trigger. In some embodiments, the system is configured to determine, based at least in part on the one or more data assets and the relevance of the risk, whether to take one or more updated actions in response to the one or more updated risk triggers, and take the one or more updated actions to remediate the risk in response to identifying the one or more updated risk triggers.

Additionally, in some implementations, the system may calculate a risk level based at least in part on the one or more updated risk triggers. The risk level may be compared to a threshold risk level for the entity. The threshold risk level may be pre-determined, or the entity may be able to adjust the threshold risk level (e.g., based on the type of data stored in the particular data asset, a number of data assets involved, etc.). In response to determining that the risk level is greater than or equal to the threshold risk level (i.e., a risk level that is defined as riskier than the threshold risk level or as risky as the threshold risk level), updating the risk remediation data to include the one or more updated actions to remediate the risk in response to identifying the one or more updated risk triggers. The risk level may be, for example, a numerical value (e.g., 1 to 10) or a described value (e.g., “low,” “medium,” or “high”), among others. In some implementations, calculating the risk level may be based at least in part on the one or more updated risk triggers further comprises comparing the one or more updated risk triggers to (i) one or more previously identified risk triggers, and (ii) one or more previously implemented actions to the one or more previously identified risk triggers.

At Step 5260, the system continues by updating the risk remediation data to include the one or more updated actions to remediate the risk in response to identifying the one or more updated risk triggers. In various embodiments, the system may automatically (e.g., substantially automatically) update the risk remediation data.

In various embodiments, the system may identify one or more risk triggers for an entity based at least in part on the update to the first data asset of the entity, and in turn, identify a second data asset of the entity potentially affected by the one or more risk triggers based at least in part on an association of a first data asset and the second data asset. The system may then determine, by using one or more data models, one or more first updated actions to remediate the one or more updated risk triggers for the first data asset, and determine, by using one or more data models, one or more second updated actions to remediate the one or more updated risk triggers for the second data asset. In some implementations, the one or more first updated actions to remediate the one or more updated risk triggers for the first data asset may be the same as or different from one or more second updated actions to remediate the one or more updated risk triggers for the second data asset. Further, the system may generate (or update) risk remediation data of the entity to include the one or more first updated actions and the one or more second updated actions to remediate the one or more potential risk triggers.

Central Consent Repository Maintenance and Data Inventory Linking

In particular embodiments, a Central Consent System is configured to provide a third-party data repository system to facilitate the receipt and centralized storage of personal data for each of a plurality of respective data subjects, as described herein. Additionally, the Central Consent System is configured to interface with a centralized consent receipt management system.

Various processes performed by the Central Consent System may be implemented by a Central Consent Module 5300. Referring to FIG. 53 , in particular embodiments, the system, when executing the Central Consent Module 5300, is configured to: identify a form used to collect one or more pieces of personal data, determine a data asset of a plurality of data assets of the organization where input data of the form is transmitted, add the data asset to the third-party data repository with an electronic link to the form in response to a user submitting the form, create a unique subject identifier associated with the user, transmit the unique subject identifier (i) to the third-party data repository and (ii) along with the form data provided by the user in the form, to the data asset, and digitally store the unique subject identifier (i) in the third-party data repository and (ii) along with the form data provided by the user in the form, in the data asset.

When executing the Central Consent Module 5300, the system begins, at Step 5310, by identifying a form used to collect one or more pieces of personal data. The particular entity may include, for example, a particular organization, company, sub-organization, etc. In particular embodiments, the one or more data assets (e.g., data systems) may include, for example, any processor or database that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, website, data-center, server, etc.). The one or more forms may ask for personal data, and the one or more data assets may store personal data for clients or customers. In embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein.

In particular embodiments, the system is configured to identify a form via one or more method that may include one or more website scanning tools (e.g., web crawling). The system may also receive an indication that a user is completing a form (e.g., a webform via a website) associated with the particular organization (e.g., a form to complete for a particular privacy campaign).

The form may include, for example, one or more fields that include the user's e-mail address, billing address, shipping address, and payment information for the purposes of collected payment data to complete a checkout process on an e-commerce website. The system may, for example, be configured to track data on behalf of an entity that collects and/or processes personal data related to: (1) who consented to the processing or collection of personal data (e.g., the data subject themselves or a person legally entitled to consent on their behalf such as a parent, guardian, etc.); (2) when the consent was given (e.g., a date and time); (3) what information was provided to the consenter at the time of consent (e.g., a privacy policy, what personal data would be collected following the provision of the consent, for what purpose that personal data would be collected, etc.); (4) how consent was received (e.g., one or more copies of a data capture form, webform, etc. via which consent was provided by the consenter); (5) when consent was withdrawn (e.g., a date and time of consent withdrawal if the consenter withdraws consent); and/or (6) any other suitable data related to receipt or withdrawal of consent.

Continuing to Step 5320, the system is configured to determine one or more data assets of a plurality of data assets of the organization where input data of the form is transmitted. In particular embodiments, the system may determine one or more data assets of the organization that receive the form data provided by the user in the form (e.g., webform). In particular embodiments, the system is configured to identify the one or more data assets using one or more data modeling techniques. As discussed more fully above, a data model may store the following information: (1) the entity that owns and/or uses a particular data asset (e.g., such as a primary data asset, an example of which is shown in the center of the data model in FIG. 4 ); (2) one or more departments within the organization that are responsible for the data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the data asset; (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to for other use, and which particular data is transferred to each of those data assets.

As may be understood in light of this disclosure, the system may utilize a data model (e.g., or one or more data models) to identify the one or more data assets associated with the particular entity that receive and/or store particular form data.

At Step 5330, the system is configured to add the one or more data assets to the third-party data repository with an electronic link to the form. In particular embodiments, a third-party data repository system may electronically link the form to the one or more data assets that processor or store the form data of the form. Next, at Step 5340, in response to a user submitting the form, the system is configured to create a unique subject identifier associated with the user. The system is configured to generate, for each data subject that completes the form (e.g., a webform), a unique identifier. The system may, for example: (1) receive an indication that the form has been completed with the form including a piece of personal data; (2) identify a data subject associated with the piece of personal data; (3) determine whether the central repository system is currently storing data associated with the data subject; and (4) in response to determining that one or more data assets of the plurality of data assets is not currently storing data associated with the data subject (e.g., because the data subject is a new data subject), generate the unique identifier.

In particular embodiments, the unique identifier may include any unique identifier such as, for example: (1) any of the one or more pieces of personal data collected, stored, and/or processed by the system (e.g., name, first name, last name, full name, address, phone number, e-mail address, etc.); (2) a unique string or hash comprising any suitable number of numerals, letters, or combination thereof; and/or (3) any other identifier that is sufficiently unique to distinguish between a first and second data subject for the purpose of subsequent data retrieval. In particular embodiments, the system is configured to assign a permanent identifier to each particular data subject. In other embodiments, the system is configured to assign one or more temporary unique identifiers to the same data subject.

In particular embodiments, the system is configured to: (1) receive an indication of completion of a form associated with the organization by a data subject; (2) determine, based at least in part on searching a unique subject identifier database (e.g., a third-party data repository), whether a unique subject identifier has been generated for the data subject; (3) in response to determining that a unique subject identifier has been generated for the data subject, accessing the unique subject identifier database; (4) identify the unique subject identifier of the data subject based at least in part on form data provided by the data subject in the completion of the form associated with the organization; and (5) update the unique subject identifier database to include an electronic link between the unique subject identifier of the data subject with each of (i) the form (e.g., including the form data) submitted by the data subject of each respective unique subject identifier, and (ii) one or more data assets that utilize the form data of the form received from the data subject. In this way, as an entity collects additional data for a particular unique data subject (e.g., having a unique subject identifier, hash, etc.), the third party data repository system is configured to maintain a centralized database of data collected, stored, and or processed for each unique data subject (e.g., indexed by unique subject identifier). The system may then, in response to receiving a data subject access request from a particular data subject, fulfill the request substantially automatically (e.g., by providing a copy of the personal data, deleting the personal data, indicating to the entity what personal data needs to be deleted from their system and where it is located, etc.). The system may, for example, automatically fulfill the request by: (1) identifying the unique subject identifier associated with the unique data subject making the request; and (2) retrieving any information associated with the unique data subject based on the unique subject identifier.

Continuing to Step 5350, the system is configured to transmit the unique subject identifier (i) to the third-party data repository and (ii) along with the form data provided by the user in the form, to the data asset. At Step 5360, the system is configured to digitally store the unique subject identifier (i) in the third-party data repository and (ii) along with the form data provided by the user in the form, in the data asset. As may understood in light of this disclosure, the system may then be configured to facilitate the receipt and centralized storage of personal data for each of a plurality of respective data subjects and the associated one or more data assets that process or store the form data provided by the data subject.

In particular embodiments, the system may be further configured for receiving a data subject access request from the user, accessing the third-party data repository to identify the unique subject identifier of the user, determining which one or more data assets of the plurality of data assets of the organization include the unique subject identifier, and accessing personal data (e.g., form data) of the user stored in each of the one or more data assets of the plurality of data assets of the organization that include the unique subject identifier. In particular embodiments, the data subject access request may be a subject's rights request where the data subject may be inquiring for the organization to provide all data that the particular organization has obtained on the data subject or a data subject deletion request where the data subject is requesting for the particular organization to delete all data that the particular organization has obtained on the data subject.

In particular embodiments, when the data subject access request is a data subject deletion request, in response to accessing the personal data of the user stored in each of the one or more data assets of the plurality of data assets of the organization that include the unique subject identifier, the system deletes the personal data of the user stored in each of the one or more data assets of the plurality of data assets of the organization that include the unique subject identifier. In some embodiments, when the data subject access request is a data subject deletion request, the system may be configured to: (1) in response to accessing the personal data of the user stored in each of the one or more data assets of the plurality of data assets, automatically determine that a first portion of personal data of the user stored in the one or more data assets has one or more legal bases for continued storage; (2) in response to determining that the first portion of personal data of the user stored in the one or more data assets has one or more legal bases for continued storage, automatically maintain storage of the first portion of personal data of the user stored in the one or more data assets; (3) in response to determining that the first portion of personal data of the user stored in the one or more data assets has one or more legal bases for continued storage, automatically maintaining storage of the first portion of personal data of the user stored in the one or more data assets; and (4) automatically facilitating deletion of a second portion of personal data of the user stored in the one or more data assets for which one or more legal bases for continued storage cannot be determined, wherein the first portion of the personal data of the user stored in the one or more data assets is different from the second portion of personal data of the user stored in the one or more data assets.

Data Transfer Risk Identification and Analysis

In particular embodiments, a Data Transfer Risk Identification System is configured to analyze one or more data systems (e.g., data assets), identify data transfers between/among those systems, apply data transfer rules to each data transfer record, perform a data transfer assessment on each data transfer record based on the data transfer rules to be applied to each data transfer record, and calculate a risk score for the data transfer based at least in part on the one or more data transfer risks associated with the data transfer record.

Various processes performed by the Data Transfer Risk Identification System may be implemented by Data Transfer Risk Identification Module 5400. Referring to FIG. 54 , in particular embodiments, the system, when executing the Data Transfer Risk Identification Module 5400, is configured for: (1) creating a data transfer record for a data transfer between a first asset in a first location and a second asset in a second location; (2) accessing a set of data transfer rules that are associated with the data transfer record; (3) performing a data transfer assessment based at least in part on applying the set of data transfer rules on the data transfer record; (4) identifying one or more data transfer risks associated with the data transfer record, based at least in part on the data transfer assessment; (5) calculating a risk score for the data transfer based at least in part on the one or more data transfer risks associated with the data transfer record; and (6) digitally storing the risk score for the data transfer.

When executing the Data Transfer Risk Identification Module 5400, the system begins, at Step 5410, by creating a data transfer record for a data transfer between a first asset in a first location and a second asset in a second location. The data transfer record may be created for each transfer of data between a first asset in a first location and a second asset in a second location where the transfer record may also include information regarding the type of data being transferred, a time of the data transfer, an amount of data being transferred, etc. In some embodiments, the system may access a data transfer record that may have already been created by the system.

In various embodiments, the system may be configured to determine in which of the one or more defined plurality of physical locations each particular data system is physically located. In particular embodiments, the system is configured to determine the physical location based at least in part on one or more data attributes of a particular data asset (e.g., data system) using one or more data modeling techniques (e.g., using one or more suitable data modeling techniques described herein). In some embodiments, the system may be configured to determine the physical location of each data asset based at least in part on an existing data model that includes the data asset. In still other embodiments, the system may be configured to determine the physical location based at least in part on an IP address and/or domain of the data asset (e.g., in the case of a computer server or other computing device) or any other identifying feature of a particular data asset.

In particular embodiments, the system is configured to identify one or more data elements stored by the one or more data systems that are subject to transfer (e.g., transfer to the one or more data systems such as from a source asset, transfer from the one or more data systems to a destination asset, etc.). In particular embodiments, the system is configured to identify a particular data element that is subject to such transfer (e.g., such as a particular piece of personal data or other data). In some embodiments, the system may be configured to identify any suitable data element that is subject to transfer and includes personal data.

In any embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein.

In some embodiments, with regard to the location of the one or more data assets, the system may define a geographic location of the one or more data assets. For example, define each of the plurality of physical locations based at least in part on one or more geographic boundaries. These one or more geographic boundaries may include, for example: (1) one or more countries; (2) one or more continents; (3) one or more jurisdictions (e.g., such as one or more legal jurisdictions); (4) one or more territories; (5) one or more counties; (6) one or more cities; (7) one or more treaty members (e.g., such as members of a trade, defense, or other treaty); and/or (8) any other suitable geographically distinct physical locations.

Continuing to Step 5420, the system is configured for accessing a set of data transfer rules that are associated with the data transfer record. The system may apply data transfer rules to each data transfer record. The data transfer rules may be configurable to support different privacy frameworks (e.g., a particular data subject type is being transferred from a first asset in the European Union to a second asset outside of the European Union) and organizational frameworks (e.g., to support the different locations and types of data assets within an organization). The applied data transfer rules may be automatically configured by the system (e.g., when an update is applied to privacy rules in a country or region) or manually adjusted by the particular organization (e.g., by a privacy officer of the organization). The data transfer rules to be applied may vary based on the data being transferred.

As may be understood from this disclosure, the transfer of personal data may trigger one or more regulations that govern such transfer. In particular embodiments, personal data may include any data which relate to a living individual who can be identified: (1) from the data; or (2) from the data in combination with other information which is in the possession of, or is likely to come into the possession of a particular entity. In particular embodiments, a particular entity may collect, store, process, and/or transfer personal data for one or more customers, one or more employees, etc.

In various embodiments, the system is configured to use one or more data models of the one or more data assets (e.g., data systems) to analyze one or more data elements associated with those assets to determine whether the one or more data elements include one or more data elements that include personal data and are subject to transfer. In particular embodiments, the transfer may include, for example: (1) an internal transfer (e.g., a transfer from a first data asset associated with the entity to a second data asset associated with the entity); (2) an external transfer (e.g., a transfer from a data asset associated with the entity to a second data asset associated with a second entity); and/or (3) a collective transfer (e.g., a transfer to a data asset associated with the entity from an external data asset associated with a second entity).

The particular entity may include, for example, a particular organization, company, sub-organization, etc. In particular embodiments, the one or more data assets (e.g., data systems) may include, for example, any entity that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, web site, data-center, server, etc.). For example, a first data asset may include any software or device utilized by a particular entity for such data collection, processing, transfer, storage, etc. In various embodiments, the first data asset may be at least partially stored on and/or physically located in a particular location. For example, a server may be located in a particular country, jurisdiction, etc. A piece of software may be stored on one or more servers in a particular location, etc.

In particular embodiments, the system is configured to identify the one or more data systems using one or more data modeling techniques. As discussed more fully above, a data model may store the following information: (1) the entity that owns and/or uses a particular data asset (e.g., such as a primary data asset, an example of which is shown in the center of the data model in FIG. 4 ); (2) one or more departments within the organization that are responsible for the data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the data asset; (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to for other use, and which particular data is transferred to each of those data assets.

As may be understood in light of this disclosure, the system may utilize a data model (e.g., or one or more data models) of data assets associated with a particular entity to identify the one or more data systems associated with the particular entity.

Next, at Step 5430, the system is configured for performing a data transfer assessment based at least in part on applying the set of data transfer rules on the data transfer record. The data transfer assessment performed by the system may identify risks associated with the data transfer record. At Step 5440, the system is configured for identifying one or more data transfer risks associated with the data transfer record, based at least in part on the data transfer assessment. The one or more data transfer risks may include, for example, a source location of the first location of the one or more first data asset of the data transfer, a destination location of the second location of the one or more second data asset of the data transfer, one or more type of data being transferred as part of the data transfer (e.g., personal data or sensitive data), a time of the data transfer (e.g., date, day of the week, time, month, etc.), an amount of data being transferred as part of the data transfer.

Continuing to Step 5450, the system is configured for calculating a risk score for the data transfer based at least in part on the one or more data transfer risks associated with the data transfer record. The risk score may be calculated in a multitude of ways, and may include one or more data transfer risks such as a source location of the data transfer, a destination location of the data transfer, the type of data being transferred, a time of the data transfer, an amount of data being transferred, etc. Additionally, the system may apply weighting factors (e.g., manually or automatically determined) to the risk factors. Further, in some implementations, the system may include a threshold risk score where a data transfer may be terminated if the data transfer risk score indicates a higher risk than the threshold risk score (e.g., the data transfer risk score being higher than the threshold risk score).

In some embodiments, the system may compare the risk score for the data transfer to a threshold risk score, determine that the risk score for the data transfer is a greater risk than the threshold risk score, and in response to determining that the risk score for the data transfer is a greater risk than the threshold risk score, taking one or more action. The one or more action may include, for example, provide the data transfer record to one or more individuals (e.g., a privacy officer) for review of the data transfer record where the one or more individuals may make a decision to approve the data transfer or terminate the data transfer. In some implementations, the system may automatically terminate the data transfer.

In some implementations, the system may generate a secure link between one or more processors associated with the first asset in the first location and one or more processors associated with the second asset in the second location, and the system may further provide the data transfer via the secure link between the one or more processors associated with the first asset in the first location and the one or more processors associated with the second asset in the second location.

In various embodiments, the system may determine a weighting factor for each of the one or more data transfer risks, determine a risk rating for each of the one or more data transfer risks, and calculate the risk level for the data transfer based upon, for each respective one of the one or more data transfer risks, the risk rating for the respective data transfer risk and the weighting factor for the respective data transfer risk.

At Step 5460, the system continues by digitally storing the risk score for the data transfer. In various embodiments, the system may continue by transferring the data between the first asset in the first location and the second asset in the second location. In some embodiments, the system may be configured to substantially automatically flag a particular transfer of data as problematic (e.g., because the transfer does not comply with an applicable regulation). For example, a particular regulation may require data transfers from a first asset to a second asset to be encrypted.

Automated Classification of Personal Information from Documents

In any embodiment described herein, an automated classification system may be configured to substantially automatically classify one or more pieces of personal information in one or more documents (e.g., one or more text-based documents, one or more spreadsheets, one or more PDFs, one or more webpages, etc.). In particular embodiments, the system may be implemented in the context of any suitable privacy compliance system, which may, for example, be configured to calculate and assign a sensitivity score to a particular document based at least in part on one or more determined categories of personal information (e.g., personal data) identified in the one or more documents. As understood in the art, the storage of particular types of personal information may be governed by one or more government or industry regulations. As such, it may be desirable to implement one or more automated measures to automatically classify personal information from stored documents (e.g., to determine whether such documents may require particular security measures, storage techniques, handling, whether the documents should be destroyed, etc.).

FIG. 55 is a flowchart of process steps that the system may perform in the automatic classification of personal information in an electronic document. When executing the Automated Classification Module 5500, the system begins, at Step 5510, by receiving and/or retrieving one or more electronic documents for analysis and classification. The system may, for example, receive a particular document from a user for analysis. In other embodiments, the system may be configured to automatically scan electronic documents stored on a system (e.g., on one or more servers, in one or more databases, or in any other suitable location) to classify any personal information that may be stored therein. In various embodiments, the one or more electronic documents may include, for example: (1) one or more PDFs; (2) one or more spreadsheets; (3) one or more text-based documents; (4) one or more audio files; (5) one or more video files; (6) one or more webpages; and/or (7) any other suitable type of document.

FIG. 56 depicts an exemplary electronic document that the system may receive and/or retrieve for analysis. As may be understood from FIG. 56 (e.g., a PDF or other text-based document), the electronic document contains employee information such as: (1) first name; (2) last name; (3) social security number; (3) address; (4) marital status; (5) phone number; (6) employer information; (7) etc.

Continuing to Step 5520, the system is configured to use one or more natural language processing techniques to determine data from the one or more electronic documents into one or more structured objects. The system may, for example, use one or more optical character recognition (OCR) techniques to identify particular text in the electronic documents. In some embodiments, the system may be configured to use one or more audio processing techniques to identify one or more words in an audio recording, etc.

The system, in particular embodiments, may be configured to: (1) parse the document to identify context for particular identified text (e.g., identify context based at least in part on proximity to other identified text, etc.); (2) parse out labels from the document; and (3) parse out values for the various labels. The system may, for example, identify particular categories of information contained in document. As may be understood from FIG. 3 , the system may be configured to identify particular labels such as, for example: (1) first name; (2) last name; (3) city; and (4) so on. The system may be further configured to identify values associated with each label such as: (1) DOE for last name; (2) JOHN for first name; (3) etc. The system may be configured to determine these values based on, for example: (1) a proximity of the values to the labels; (2) a position of the values relative to the labels; (3) one or more natural language processing techniques (e.g., the system may be configured to identify John as a name, and then associate John with the identified label for name, etc.). The system may then be further configured to electronically associate the identified values with their respective labels (e.g., in computer memory).

In any embodiment described herein, the system may then generate a classification of one or more structured objects identified using the natural language processing techniques described above. For example, the system may be configured to generate a catalog of labels identified in the electronic document. FIG. 57 depicts an illustration of one or more object that the system has generated based on the document shown in FIG. 56 as a result of the scanning described above.

Continuing to Step 5530, the system is configured to classify each of the one or more structured objects based on one or more attributes of the structured objects. For example, the system may be configured to use contextual information, sentiment, and/or syntax to classify each of the structured objects. FIG. 58 depicts an exemplary classification of the structured objects cataloged from FIG. 57 . As may be understood from this Figure, the system may be configured to group objects based in part on a type of information. For example, the various objects related to an individual's name (e.g., first name, last name, etc.) may be grouped into a single classification. The system may, for example, be configured to automatically classify the one or more objects based on: (1) the object's proximity in the particular document; (2) one or more headings identified in the document; and/or (3) any other suitable factor. For example, in various embodiments, the system is configured to use one or more machine learning and/or natural language techniques to identify a relation between objects.

The system may then be configured to identify one or more objects without associated values and remove those objects from the classification. FIGS. 59-60 depict a visual representation of objects without associated values from the PDF shown in FIG. 56 being blacked out and removed from the classification. The system may, for example, be configured to generate an initial classification based on the document, and then modify the classification based on one or more identified values in the specific document.

Continuing to Step 5540, the system is configured to categorize each of the one or more structured objects based at least in part on a sensitivity of information determined based on the one or more attributes of the objects. The system may be configured to determine the categorization based on sensitivity based on, for example: (1) one or more predefined sensitivities for particular categories of information; (2) one or more user-defined sensitivities; (3) one or more sensitivities determined automatically based on one or more prevailing industry or government regulations directed toward the type of information associated with the objects; (4) etc.

FIG. 62 depicts an exemplary mapping of values and structured objects based on a sensitivity of the structured objects. As may be understood from this figure, the system is configured to cross-reference the categorization of structured objects with a database of personal data classification, which may, for example, identify a sensitivity of particular categories of structured objects (e.g., personally identifiable information, sensitive personal data, partial PII, personal data, not personal data, etc.). The system may then be configured to map the results as shown in FIG. 62 .

Next, at Step 5550, the system is configured to rate the accuracy of the categorization performed at Step 5540. The system may, for example, be configured to rate the categorization by comparing the categorization determined for a similar electronic document (e.g., a second electronic document that includes the same form filled out by another individual than John Doe). In other embodiments, the system may be configured to rate the accuracy of the categorization based on one or more attributes (e.g., one or more values) of the structured objects. The system may, for example, analyze the value for a particular object to determine an accuracy of the categorization of the object. For example, an object for first name may be categorized as “employee information,” and the system may be configured to analyze a value associated with the object to determine whether the categorization is accurate (e.g., analyze the value to determine whether the value is, in fact, a name). The system may, for example, determine that the accuracy of the categorization is relatively low in response to determining that a value for the “first name” object contains a number string or a word that is not traditionally a name (e.g., such as ‘attorney’ or another job title, a phone number, etc.). The system may determine a character type (e.g., set of numbers, letters, a combination of numbers and letters, etc.) for each object and a character type for each value of the object to determine the accuracy of the categorization. The character type for each object and each value of the object may be compared to determine the accuracy of the categorization by the system.

Continuing to Step 5560, the system is configured to generate a sensitivity score for each element in the one or more electronic documents and each document as a whole based at least in part on the category and sensitivity of each object. The system may, for example, assign a relative sensitivity to the document based on each relative sensitivity score assigned to each object identified in the document. The system may, in various embodiments, calculate a sensitivity score for each object based at least in part on a confidence in the accuracy of the categorization of the object and the sensitivity assigned to the particular categorization.

CONCLUSION

Although embodiments above are described in reference to various privacy compliance monitoring systems, it should be understood that various aspects of the system described above may be applicable to other privacy-related systems, or to other types of systems, in general.

While this specification contains many specific embodiment details, these should not be construed as limitations on the scope of any invention or of what may be Concepted, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially Concepted as such, one or more features from a Concepted combination may in some cases be excised from the combination, and the Concepted combination may be directed to a sub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended Concepts. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for the purposes of limitation.

Although embodiments above are described in reference to various data subject access fulfillment systems, it should be understood that various aspects of the system described above may be applicable to other privacy-related systems, or to other types of systems, in general.

While this specification contains many specific embodiment details, these should not be construed as limitations on the scope of any invention or of what may be Concepted, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially Concepted as such, one or more features from a Concepted combination may in some cases be excised from the combination, and the Concepted combination may be directed to a sub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. In addition, it should be understood that terms such as “in some embodiments”, “in various embodiments”, and “in certain embodiments” are intended to indicate that the stated features may be implemented in any suitable embodiment described herein.

Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended Concepts. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for the purposes of limitation. 

What is claimed is:
 1. A method comprising: accessing, by computing hardware, a data model comprising a data structure representing a data asset that comprises at least one of software or hardware device within a computing system, wherein the data model comprises an inventory comprising a plurality of attributes that defines (i) personal data stored on the data asset and (ii) processing activities that are performed within the computing system and are associated with the personal data; analyzing, by the computing hardware, the data model to identify a first portion of the personal data that is associated with a terminated processing activity of the processing activities, wherein the plurality of attributes identifies the first portion of the personal data is associated with the terminated processing activity; and facilitating, by the computing hardware, removal of the first portion of the personal data from being stored on the data asset.
 2. The method of claim 1, further comprising: analyzing, by the computing hardware, the data model to identify a second portion of the personal data that is not associated with any of the processing activities; and facilitating, by the computing hardware, removal of the second portion of the personal data from being stored on the data asset.
 3. The method of claim 1, further comprising: scanning, by the computing hardware, the data asset to identify the personal data stored on the data asset and the processing activities that are performed within the computing system and are associated with the personal data to generate a catalog of the personal data; and scanning, by the computing hardware, the data asset based on the generated catalog to generate the data model.
 4. The method of claim 1, wherein facilitating of the first portion of the personal data from being stored on the data asset comprises at least one of: generating a user interface that includes an indication of the first portion of the personal data, or generating and transmitting an instruction to a third party system regarding removal of the first portion of the personal data from the data asset.
 5. The method of claim 1, further comprising: accessing, by the computing hardware, data retention parameters for the data asset, wherein the data retention parameters comprise: (a) a first parameter defining a time period within which the personal data must be removed; and (b) a second parameter identifying a triggering event for removal of the first portion of the personal data; and facilitating, by the computing hardware, the removal of the first portion of the personal data from being stored on the data asset is performed according to the data retention parameters by facilitating at least one of: (a) the removal of the personal data from the data asset within the time period; or (b) the removal of the personal data from the data asset in response to identifying an occurrence of the triggering event.
 6. The method of claim 1, further comprising: generating, by the computing hardware, a graphical user interface based on the first portion of the personal data by configuring a control element configured to generate a request to remove the first portion of the personal data from being stored on the data asset and a presentation element configured for presenting an indication of the first portion of the personal data; transmitting, by the computing hardware, an instruction to an application executing on a user device causing the application to present the graphical user interface on the user device; and facilitating, by the computing hardware, the removal of the first portion of the personal data from being stored on the data asset in response to a selection of the control element.
 7. The method of claim 1, further comprising: receiving, by the computing hardware, an indication of a new processing activity that is associated with the personal data; and responsive to the indication of the new processing activity, modifying, by the computing hardware, the plurality of attributes to identify an association between the new processing activity and a piece of the personal data.
 8. The method of claim 1, wherein facilitating of the first portion of the personal data comprises modifying metadata associated with the first portion of the personal data to indicate that the first portion of the personal data is orphaned data.
 9. A system comprising: processing hardware; computer memory communicatively coupled to the processing hardware; and a non-transitory computer-readable medium communicatively coupled to the processing hardware, and storing computer-executable instructions, wherein the processing hardware is configured for executing the computer-executable instructions and thereby performing operations comprising: accessing a data asset comprising at least one of software or a hardware device used within a computing system; scanning data fields of the data asset to identify personal data stored on the data asset that is utilized by processing activities performed within the computing system to generate a catalog of the processing activities and the personal data, wherein the catalog comprising a plurality of attributes that defines (i) the personal data stored on the data asset and (ii) processing activities that are performed within the computing system and are associated with the personal data; identifying a portion of the personal data that is associated with each processing activity of the processing activities; scanning the data asset based on the generated catalog to identify a first portion of the personal data that is no longer associated with a first processing activity of the processing activities, wherein the plurality of attributes identifies the first portion of the personal data is no longer associated with the first processing activity of the processing activities; and facilitating of the first portion of the personal data from being stored on the data asset.
 10. The system of claim 9, wherein the operations further comprise: generating a graphical user interface based on the first portion of the personal data by configuring a control element configured to generate a request to remove the first portion of the personal data from being stored on the data asset and a presentation element configured for presenting an indication of the first portion of the personal data; transmitting an instruction to an application executing on a user device causing the application to present the graphical user interface on the user device; and facilitating of the first portion of the personal data from being stored on the data asset in response to a selection of the control element.
 11. The system of claim 9, wherein the operations further comprise: scanning the data asset based on the generated catalog to identify a second portion of the personal data that is associated with a terminated processing activity of the processing activities; and facilitating of the second portion of the personal data from the data asset.
 12. The system of claim 9, wherein the operations further comprise: accessing a data retention parameter for the data asset, the data retention parameter defining a time period for the removal of the first portion of the personal data; and facilitating of the first portion of the personal data from being stored on the data asset according to the data retention parameter by facilitating of the first portion of the personal data after the time period.
 13. The system of claim 9, wherein the operations further comprise generating a data model that maps an association between each piece of the personal data stored on the data asset and a respective processing activity of the processing activities.
 14. The system of claim 13, wherein the operations further comprise: analyzing the data model to identify a second portion of the personal data that is associated with a terminated processing activity of the processing activities; and facilitating of the second portion of the personal data from the data asset.
 15. A method comprising: accessing, by computing hardware, a data model comprising a data structure representing a data asset that comprises at least one of software or hardware device within a computing system, wherein the data model comprises an inventory comprising a plurality of attributes that defines (i) personal data stored on the data asset and (ii) processing activities that are performed within the computing system and are associated with the personal data; analyzing, by the computing hardware, the data model to identify a portion of the personal data that is not associated with an active processing activity of the processing activities, wherein the plurality of attributes identifies the portion of the personal data is not associated with the active processing activity of the processing activities; and facilitating, by the computing hardware, removal of the portion of the personal data from being stored on the data asset.
 16. The method of claim 15, wherein the portion of the personal data comprises data that is associated with a terminated processing activity of the processing activities.
 17. The method of claim 15, further comprising: generating, by the computing hardware, a graphical user interface based on the portion of the personal data by configuring a control element configured to generate a request to remove the portion of the personal data from being stored on the data asset and a presentation element configured for presenting an indication of the portion of the personal data; transmitting, by the computing hardware, an instruction to an application executing on a user device causing the application to present the graphical user interface on the user device; and facilitating, by the computing hardware, the removal of the portion of the personal data from being stored on the data asset in response to a selection of the control element.
 18. The method of claim 15, further comprising: scanning, by the computing hardware, the data asset to identify the personal data stored on the data asset and the processing activities that are performed within the computing system and are associated with the personal data to generate a catalog of the personal data; and scanning, by the computing hardware, the data asset based on the generated catalog to generate the data model.
 19. The method of claim 15, further comprising: accessing, by the computing hardware, a data retention parameter for the data asset, the data retention parameter defining: (a) a first parameter defining a time period for removing the personal data; and (b) a second parameter identifying a triggering event for removing the first portion of the personal data; and facilitating, by the computing hardware, the removal of the first portion of the personal data from the data asset according to the data retention parameter by facilitating at least one of: (a) the removal of the personal data from the data asset within the time period; or (b) the removal of the personal data from the data asset in response to identifying an occurrence of the triggering event.
 20. The method of claim 15, wherein facilitating of the portion of the personal data comprises modifying metadata associated with the portion of the personal data to indicate that the portion of the personal data is orphaned data. 